• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Improvements in the OOo Release

Improvements in the OOo Release



Improvements on the release Process

Improvements on the release Process



Total Views
Views on SlideShare
Embed Views



1 Embed 2

https://www.linkedin.com 2



Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • scp2 delivers scripts, containing full description of files, directories, CustomActions, … ESP: Easy Software Products EPM: ESP Package Manager
  • Last point: instsetoo_native “knows” the product information -> change to next slide: “What contains the product defintion?”
  • Not all 51 databases of a database dynamic Some are static -> better performance Especially GUI description tables
  • Used to differentiate between OOo and OOo DEV -> otherwise both have the same content (same scripts, same pathes, same static msi tables).
  • Starting with: “Around the central Perl packaging program, there are several ...”
  • msm for the Microsoft runtime libraries, that are system wide installed. mst for multilingual installation sets.
  • Also Windows integration of Merge modules for Microsoft Runtime libraries ...
  • “ With this final slide for the packaging framework I want to stress, that packaging of files is not all, as the one or the other might think.”
  • The packaging process is very dynamic. Performance improvements by package pool Windows minor upgrade very complex because of database analysis.
  • We want to reduce the number of installation sets and not increase it.

Improvements in the OOo Release Improvements in the OOo Release Presentation Transcript

  • Installation and Packaging – Presence and Future Dr. Ingo Schmidt-Rosbiegal Project Lead OpenOffice.org Installation Sun Microsystems OOoCon 2009, Orvieto, Italy
  • Agenda
    • The Packaging Framework
    • What is new in OpenOffice.org 3 ?
    • Plans for the Future
  • The Packaging Framework The existing packaging and installation framework:
    • Was introduced with OOo 2.0, replacing the platform independent installer
    • Was motivated by the support of native installer techniques (Windows Installer, Solaris packages, Linux RPMs, …)
    • Is completely based on OpenSource tools
    • Includes several source code modules
  • The Packaging Framework 6 Modules for packaging/installation
    • scp2 : Platform independent description language of product content (files, dirs, links, registry, ...)
    • setup_native : Helper programs for packaging, CustomActions, S hell scripts, Package defs, ...
    • epm : External helper program, ESP package manager (www.epmhome.org)
    • javainstaller2 : Java GUI Installer for Unixes
    • instsetoo_native : Product definitions and packaging, only module “knowing products”
    • solenv : Perl packaging tooling
  • The Packaging Framework Tooling contains Installation sets Helper programs
  • The Packaging Framework Defining a Product: (3x instsetoo_native, 1x scp2)
  • The Packaging Framework The Meaning of the Properties: -> many switches for the product
  • The Packaging Framework Helper Programs:
  • The Packaging Framework Supported installation set formats:
  • The Packaging Framework 9 defined products in instsetoo_native:
    • OpenOffice.org, also with JRE
    • OOo SDK
    • OOo Dev
    • OOo Dev SDK
    • BrOffice.org, also with JRE
    • BrOffice.org Dev
    • URE
  • The Packaging Framework Creating an installation set: A B C
  • The Packaging Framework Packaging of files is not all:
    • Many more scp items: Registry, StartMenu, CustomActions, Shell scripts, …
    • Files are unzipped, created (services.rdb, ini-files), changed (Customization), compressed, registered, filtered (Language Packs), …
    • Full support of Windows Installer technology
    • Unix: Pool administration for packages
    • and much, much more ...
  • What is new in OpenOffice.org 3 ? Most visible changes:
    • 3-Layer Office (Brand, Basis, URE)
    • Java GUI Installer for OOo with JRE (OOo 2.4)
    • Minor Upgrade for Windows 3.0.1
    • Package Pool for Linux rpm and Solaris (increasing packaging performance)
    • Windows: Integration of Windows Installer Merge modules msi database
    • Customization with “extension” folder (Windows)
  • Plans for the Future Two motivations for changes:
  • Plans for the Future Chainer:
    • has a modern GUI, knows dependencies between packages and is included into Add-Remove-Software-Applet (not the micro packages).
    • is responsible for installation, maintenance, update and deinstallation of the product.
    • has to be created for each product individually.
    • needs WI 4.5 concerning to MS -> not for old Windows versions (min. Win XP SP 3)
  • Plans for the Future Idea:
  • Plans for the Future Installation process:
  • Plans for the Future Two kinds of installation: A B
  • Plans for the Future Java GUI Installer as Chainer has to be:
    • Product inpependent : Configuration files define the product during runtime
    • Language independent : Java jar file contains all available localizations
    • Platform independent : Java jar file contains all informations about native installer processes
    • Flexible : The number of packages next to the Java jar file has to be flexible -> adding a new OOo language by adding the package
  • Plans for the Future Advantages:
    • For each product, only one multi-lingual installation set is still required. Language selection happens online before download.
    • Less upload, less redundancies (DLLs, ...).
    • More releases can be made available online.
    • Less download, because module and language selection happens before download starts.
    • QA concentrated on one installation set.
  • Plans for the Future Advantages:
    • Simplified language handling, no language packs required. Only install maintenance mode.
    • Introduction of a Chainer, that supports micro-msi-packages also on older Windows systems.
    • msi databases separated like RPMs. Better modularization and easier development.
    • Micro-msi-packages can be in Pool process.
    • Unique installer appearance on all platforms, but using native installer.
  • Summary The packaging and installation framework was presented and the most visible new features for OOo 3 were introduced. The plan for the future is the consolidation of installation and download leading to a dramatic reduction of installation sets. This can be realized by the Java GUI Installer, that needs to become a Chainer also for Windows msi packages.
  • Installation and Packaging - Presence and Future Dr. Ingo Schmidt-Rosbiegal [email_address]