Improvements in the OOo Release


Published on

Improvements on the release Process

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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

    1. 1. Installation and Packaging – Presence and Future Dr. Ingo Schmidt-Rosbiegal Project Lead Installation Sun Microsystems OOoCon 2009, Orvieto, Italy
    2. 2. Agenda <ul><li>The Packaging Framework
    3. 3. What is new in 3 ?
    4. 4. Plans for the Future </li></ul>
    5. 5. The Packaging Framework The existing packaging and installation framework: <ul><li>Was introduced with OOo 2.0, replacing the platform independent installer
    6. 6. Was motivated by the support of native installer techniques (Windows Installer, Solaris packages, Linux RPMs, …)
    7. 7. Is completely based on OpenSource tools
    8. 8. Includes several source code modules </li></ul>
    9. 9. The Packaging Framework 6 Modules for packaging/installation <ul><li>scp2 : Platform independent description language of product content (files, dirs, links, registry, ...)
    10. 10. setup_native : Helper programs for packaging, CustomActions, S hell scripts, Package defs, ...
    11. 11. epm : External helper program, ESP package manager (
    12. 12. javainstaller2 : Java GUI Installer for Unixes
    13. 13. instsetoo_native : Product definitions and packaging, only module “knowing products”
    14. 14. solenv : Perl packaging tooling </li></ul>
    15. 15. The Packaging Framework Tooling contains Installation sets Helper programs
    16. 16. The Packaging Framework Defining a Product: (3x instsetoo_native, 1x scp2)
    17. 17. The Packaging Framework The Meaning of the Properties: -> many switches for the product
    18. 18. The Packaging Framework Helper Programs:
    19. 19. The Packaging Framework Supported installation set formats:
    20. 20. The Packaging Framework 9 defined products in instsetoo_native: <ul><li>, also with JRE
    21. 21. OOo SDK
    22. 22. OOo Dev
    23. 23. OOo Dev SDK
    24. 24., also with JRE
    25. 25. Dev
    26. 26. URE </li></ul>
    27. 27. The Packaging Framework Creating an installation set: A B C
    28. 28. The Packaging Framework Packaging of files is not all: <ul><li>Many more scp items: Registry, StartMenu, CustomActions, Shell scripts, …
    29. 29. Files are unzipped, created (services.rdb, ini-files), changed (Customization), compressed, registered, filtered (Language Packs), …
    30. 30. Full support of Windows Installer technology
    31. 31. Unix: Pool administration for packages
    32. 32. and much, much more ... </li></ul>
    33. 33. What is new in 3 ? Most visible changes: <ul><li>3-Layer Office (Brand, Basis, URE)
    34. 34. Java GUI Installer for OOo with JRE (OOo 2.4)
    35. 35. Minor Upgrade for Windows 3.0.1
    36. 36. Package Pool for Linux rpm and Solaris (increasing packaging performance)
    37. 37. Windows: Integration of Windows Installer Merge modules msi database
    38. 38. Customization with “extension” folder (Windows) </li></ul>
    39. 39. Plans for the Future Two motivations for changes:
    40. 40. Plans for the Future Chainer: <ul><li>has a modern GUI, knows dependencies between packages and is included into Add-Remove-Software-Applet (not the micro packages).
    41. 41. is responsible for installation, maintenance, update and deinstallation of the product.
    42. 42. has to be created for each product individually.
    43. 43. needs WI 4.5 concerning to MS -> not for old Windows versions (min. Win XP SP 3) </li></ul>
    44. 44. Plans for the Future Idea:
    45. 45. Plans for the Future Installation process:
    46. 46. Plans for the Future Two kinds of installation: A B
    47. 47. Plans for the Future Java GUI Installer as Chainer has to be: <ul><li>Product inpependent : Configuration files define the product during runtime
    48. 48. Language independent : Java jar file contains all available localizations
    49. 49. Platform independent : Java jar file contains all informations about native installer processes
    50. 50. Flexible : The number of packages next to the Java jar file has to be flexible -> adding a new OOo language by adding the package </li></ul>
    51. 51. Plans for the Future Advantages: <ul><li>For each product, only one multi-lingual installation set is still required. Language selection happens online before download.
    52. 52. Less upload, less redundancies (DLLs, ...).
    53. 53. More releases can be made available online.
    54. 54. Less download, because module and language selection happens before download starts.
    55. 55. QA concentrated on one installation set. </li></ul>
    56. 56. Plans for the Future Advantages: <ul><li>Simplified language handling, no language packs required. Only install maintenance mode.
    57. 57. Introduction of a Chainer, that supports micro-msi-packages also on older Windows systems.
    58. 58. msi databases separated like RPMs. Better modularization and easier development.
    59. 59. Micro-msi-packages can be in Pool process.
    60. 60. Unique installer appearance on all platforms, but using native installer. </li></ul>
    61. 61. 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.
    62. 62. Installation and Packaging - Presence and Future Dr. Ingo Schmidt-Rosbiegal [email_address]