Difference between revisions of "User:Kr/Packaging"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (→‎Red Hat Package Manager / YUM: Moved to Efforts/Package_Restructuring/Backends/Red_Hat_Package_Manager/YUM)
m (→‎Implementations: Moved to Efforts/Package_Restructuring/Backends)
 
(5 intermediate revisions by the same user not shown)
Line 101: Line 101:
  
  
−
==Implementations==
 
−
Example Product creation for by target deployment system.
 
  
−
===Capabilities===
 
−
Please see [[Package_Formats%26Repositories]]
 
−
 
−
====Product View====
 
−
All of our package oriented target deployment system lack a Product View. This has been recognized already some while, when we switched to native installers, and lead to the Java Installer, basically offering a Product View similar to MS Windows "Add or Remove Programs" approach.
 
−
 
−
To establish a Product View, we need to now
 
−
* which parts of a particular are already installed, and
 
−
* which parts are additionally available.
 
−
 
−
====Repository Support====
 
−
To integrate into deployment systems using external repositories for updating / maintaining a system, we need to be able to
 
−
* add a repository (e.g. repository.openoffice.org) during installation, respectively to
 
−
* remove a repository during de-installation.
 
−
 
−
 
−
====Debian Packages / APT====
 
−
DPKG / APT, similar to RPM / YUM  or RPM / YaST, delegate responsibilities for managing already installed packages respectively for retrieving updates as well as managing a package pool (the repository) with packages of different sources.
 
−
 
−
=====Repository Support=====
 
−
To my knowledge there is no command line tool around, to modify the APT repository list (apt/sources.list) except apt-cdrom, which is used to add and register CDs only. Fortunately there is this "libapt-pkg" library, providing programmatic access to apt and hopefully supporting addition and removal of repositories.
 
−
 
−
=====Product View=====
 
−
Having Repository Support for APT would allow us, to leverage APT to achieve download installation as well as maintenance and would ease dependency handling, as this is already covered.
 
−
 
−
To query for the installed packages of a particular product (e.g. OOo):
 
−
<pre>
 
−
~> dpkg -l "openoffice.org-*" | grep "^in"
 
−
in  openoffice.org-core01            <none>        (no description available)
 
−
in  openoffice.org-core02            <none>        (no description available)
 
−
in  openoffice.org-core03            <none>        (no description available)
 
−
in  openoffice.org-core03u            <none>        (no description available)
 
−
in  openoffice.org-core04            <none>        (no description available)
 
−
in  openoffice.org-core04u            <none>        (no description available)
 
−
...
 
−
</pre>
 
−
To query for all available packages of a particular product (e.g. OOo):
 
−
<pre>
 
−
~> apt-cache dumpavail | grep -i "^package.*openoffice"
 
−
Package: openoffice.org-filter-so52
 
−
Package: openoffice.org-gtk-gnome
 
−
Package: openoffice.org-help-en
 
−
Package: openoffice.org-hyphenation-hr
 
−
...
 
−
</pre>
 
−
 
−
To find the files belonging to a particular package, including the Java Installer .xpd files:
 
−
<pre>
 
−
~> dpkg -L openoffice.org-writer
 
−
/.
 
−
/usr
 
−
/usr/lib
 
−
/usr/lib/openoffice
 
−
/usr/lib/openoffice/program
 
−
/usr/lib/openoffice/program/libwpft680lx.so
 
−
/usr/lib/openoffice/program/liblwpft680lx.so
 
−
/usr/lib/openoffice/program/libmsworks680lx.so
 
−
/usr/lib/openoffice/program/libswui680lx.so
 
−
...
 
−
</pre>
 
−
 
−
What we don't have yet is the .xpd information for not yet installed (downloaded) features. As a workaround, we could put the xpd description into a packages description, this would be enough information to start the Java Installer (the Product View) for any product.
 
−
 
−
 
−
 
−
====Red Hat Package Manager / YaST====
 
−
=====Product View=====
 
−
=====Repository Support=====
 
−
 
−
=====Links=====
 
−
http://en.wikipedia.org/wiki/Yast
 
−
 
−
====Mac OS X====
 
−
Links:
 
−
* [http://developer.apple.com/documentation/DeveloperTools/FilesSoftwareInstallation-date.html Files & Software Installation]
 
−
* [http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGInstallationsUpdates/chapter_9_section_1.html Software Installation and Software Updates]
 
−
=====Product View=====
 
−
=====Repository Support=====
 
−
 
−
====Solaris Packages====
 
−
=====Product View=====
 
−
=====Repository Support=====
 
−
 
−
====MS Windows Installer Service====
 
−
Experiments under Windows with [http://sourceforge.net/projects/wix/ WiX (Windows Installer XML)] show,
 
−
* that any set of products may share any number of files,
 
−
* that any one product may update any number of other products (basically leading to a de-installation of these other products), and
 
−
* that any product sharing files with other products may update any number of these shared files.
 
−
 
−
This lets me think, that Windows is as dynamic and flexible as the classic package based platforms, while providing a simpler user interface.
 
−
 
−
;Merge Modules: "In order to avoid versioning problems, you should use always merge modules for any component or file that will be shared by multiple applications." [http://msdn2.microsoft.com/en-us/library/0h4bhcz3(VS.71).aspx]
 
−
 
−
;Product Independent Updates: To realize product independent updates I basically see two options,
 
−
* try to use the Installer API[http://msdn2.microsoft.com/en-us/library/aa369425%28VS.85%29.aspx] to install/update shared "components" programmatically, or
 
−
* split OOo into hierarchical dependent products (e.g. URE, CORE, brands), which are to be installed concurrently (see Concurrent Installations[http://msdn2.microsoft.com/en-us/library/aa368010(VS.85).aspx]) and may utilize product hiding[http://msdn2.microsoft.com/en-us/library/aa367750(VS.85).aspx] (e.g. for the CORE) in the "Add and Remove Programs" dialogue.
 
−
 
−
=====Product View=====
 
−
=====Repository Support=====
 
−
MS Windows uses the WSUS (Windows Server Update Services)[http://technet.microsoft.com/en-us/wsus/default.aspx] to keep Windows and MS applications current. With the latest version, so called "Local Publishing" by using the WSUS API becomes possible[http://msdn2.microsoft.com/en-us/library/aa970328.aspx]. This may be an opportunity to enable WSUS to publish OOo updates ...
 
−
 
−
WSUS Links:
 
−
http://www.microsoft.com/technet/community/en-us/sus/default.mspx
 
  
 
==Links==
 
==Links==

Latest revision as of 09:36, 25 January 2008

Todos:

  • Split this into multiple pages.
  • Add testing, testability and QA.
  • List the stakeholders.
  • Add "few deliverables as possible" goal.
  • Add 3rd party staff to be separated.


Overview

Some clarification is needed regarding the terms to describe how to deploy, update, maintain and configure a particular software program.

Products

A product consists of a particular set of features and localizations targeted to a particular set of platforms and deployment systems. A product is a set of bits provided by a medium such as a CD, a floppy disk or as a download. A product typically has a brand as well as predecessor and successor products and may require other products to be installed. Independent Products assembled of other (sub-) products may share these (sub-) products, even if these (sub-) products are implementation details only.

Deployment

As OOo is cross platform (Operating System / Machine Architecture), OOo installation sets need to integrate with different deployment systems.

These deployment systems can be categorized as to be

  • package oriented (such as RPM) and / or
  • product oriented (such as MS Windows Installer).

Package Support

Package oriented deployment systems typically lack product support, e.g. in a package oriented deployment system, the user typically only sees the deployed packages in the systems configuration and is neither able to directly see which products are represented by which packages, nor which additional features are available. To remove a particular product the user needs to find and to remove all belonging packages (sometimes even the indirectly installed packages) typically by searching the package database.

Package oriented deployment systems enable sharing of packages between products, allowing for re-usage of particular files or functionalities.

Packages can typically be set into relationship to one another. The following are typical relationships,

  • one package may require on one or many another packages,
  • one package may conflict with one or many other packages,
  • one package may replace one or many other packages,
  • one package may suggest one or many other packages.

Program updates may be deployed at least on a package granularity, while some deployment systems even support patch packages (packages which only contain the differences between a particular package and its successor).

Product Support

In a product oriented deployment system, the user sees the installed products in the systems configuration. Customization is typically supported by product, offering not yet installed features as well as allowing to remove the product as a whole.

Product based deployment systems may allow sharing of entities (e.g. files) on some level (e.g. "component", see below).

Product based deployment systems typically allow to set products into predecessor / successor relationship.

Product based deployment systems mostly only support product updates on a product level, e.g. as new products or as product patches, which may only be applied to one particular product.

Updates

Over time, new versions of products are released, providing bug fixes, additional features, usability improvements etc. During the deployment of product updates the older versions may be de-installed or altered respectively completed. Updates may be provided as dedicated products or as implicit downloads.


Requirements

Compatibility

As a product evolves, its interfaces may change in an incompatible fashion. For binary packages mostly interesting are

  • ABI (Application Binary Interface) incompatible changes, as well as
  • structural incompatible changes (removed / renamed files).

Some installation units try to stay compatible, expressing any change of compatibility in their version numbers, while others may change incompatible with every version.

Version numbers expressing compatibility are typically used as follows,

  • a change in the micro version signals for bug fixes only,
  • a change in a minor version signals additional features,
  • a change in the major signals an incompatible (API / ABI etc.) change.

The OOo productizer needs to support compatibility changes, such that different versions and derivatives may be installed without conflict side by side.

Deployment Systems

Deployment systems to be supported by OOo are at least

Developers

Support for Changes:

  • updated package(s)
  • (automatically) remove package(s)
  • add package(s)
  • rename package(s)
  • remove file(s)
  • add file(s)
  • move file(s)

Program Management

In a perfect world, program management would be able to create any kind of product, only depending on business needs, not restricted by technical constraints.

Program Management basically mediates between marketing / market requirements and the pool of available technologies.

Program management requires the following product relationships to be supported:

  • No relationship -> self contained
  • Update relationship
    • update only (e.g. add-ons, localizations)
    • self contained (e.g. OOo 2.1 updating OOo 2)
    • Multi-update relationship
      • Cross version (major / minor / micro)
      • Cross language
      • Cross brand
      • Cross variant
      • Cross platform



Links

Retrieved from "https://wiki.openoffice.org/w/index.php?title=User:Kr/Packaging&oldid=61670"
Personal tools