Difference between revisions of "Efforts/Packaging"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Packaging Effort)
 
m (Moved Intro from User:Kr/Packaging here.)
Line 1: Line 1:
 
Type: [[Uno/Term/Effort|Effort]] Status: in progress  Owner: [[User:Sb|Stephan Bergmann]] ([[KR|Kay Ramme]])
 
Type: [[Uno/Term/Effort|Effort]] Status: in progress  Owner: [[User:Sb|Stephan Bergmann]] ([[KR|Kay Ramme]])
  
 +
OpenOffice.org (OOo) and its derivatives are complex products. Many features, templates, configuration files, registry entries, binaries, localizations etc. need to be delivered and deployed in a reliable and platform compliant way, while giving the user broad choice regarding the particular features he wants to actually install.
 +
 +
OOos growing ecosystem brings the current approach to its limits, we are currently facing a set of problems, which the below proposed solution is going to address. OOo based products need to support different platforms (Operating System / Machine Architecture) as well as different deployment systems (e.g. [http://www.rpm.org RPM], [http://en.wikipedia.org/wiki/Dpkg Debian Packages], Ports, Solaris Packages, [http://msdn2.microsoft.com/en-us/library/aa372866.aspx MS Windows Installer]), localizations and feature sets, as well as they need to be easy to extend and maintain.
  
 
==Problem==
 
==Problem==
Line 8: Line 11:
  
 
==Time Frame==
 
==Time Frame==
 +
Roughly OOo 3.0.
  
 
==Tasks==
 
==Tasks==

Revision as of 10:16, 21 January 2008

Type: Effort Status: in progress Owner: Stephan Bergmann (Kay Ramme)

OpenOffice.org (OOo) and its derivatives are complex products. Many features, templates, configuration files, registry entries, binaries, localizations etc. need to be delivered and deployed in a reliable and platform compliant way, while giving the user broad choice regarding the particular features he wants to actually install.

OOos growing ecosystem brings the current approach to its limits, we are currently facing a set of problems, which the below proposed solution is going to address. OOo based products need to support different platforms (Operating System / Machine Architecture) as well as different deployment systems (e.g. RPM, Debian Packages, Ports, Solaris Packages, MS Windows Installer), localizations and feature sets, as well as they need to be easy to extend and maintain.

Problem

Approach

Analyse the current state. Find and propose a solution, and implement it.

Time Frame

Roughly OOo 3.0.

Tasks

Title Effort
Generalize Java Installer to support arbitrary repository and package managers --
Basic De-Composition (Uno,Bases/Core/Apps,Brand,localization) --
Find a way to update MS Windows Installer Components in a product independent way --
Personal tools