12. javainstaller2 : Java GUI Installer for Unixes
13. instsetoo_native : Product definitions and packaging, only module “knowing products”
14. solenv : Perl packaging tooling </li></ul>
15. The Packaging Framework Tooling contains Installation sets Helper programs
16. The Packaging Framework Defining a Product: (3x instsetoo_native, 1x scp2)
17. The Packaging Framework The Meaning of the Properties: -> many switches for the product
18. The Packaging Framework Helper Programs:
19. The Packaging Framework Supported installation set formats:
20. The Packaging Framework 9 defined products in instsetoo_native: <ul><li>OpenOffice.org, also with JRE
21. OOo SDK
22. OOo Dev
23. OOo Dev SDK
24. BrOffice.org, also with JRE
25. BrOffice.org Dev
26. URE </li></ul>
27. The Packaging Framework Creating an installation set: A B C
28. The Packaging Framework Packaging of files is not all: <ul><li>Many more scp items: Registry, StartMenu, CustomActions, Shell scripts, …
29. Files are unzipped, created (services.rdb, ini-files), changed (Customization), compressed, registered, filtered (Language Packs), …
30. Full support of Windows Installer technology
31. Unix: Pool administration for packages
32. and much, much more ... </li></ul>
33. What is new in OpenOffice.org 3 ? Most visible changes: <ul><li>3-Layer Office (Brand, Basis, URE)
34. Java GUI Installer for OOo with JRE (OOo 2.4)
35. Minor Upgrade for Windows 3.0.1
36. Package Pool for Linux rpm and Solaris (increasing packaging performance)
37. Windows: Integration of Windows Installer Merge modules msi database
38. Customization with “extension” folder (Windows) </li></ul>
39. Plans for the Future Two motivations for changes:
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. is responsible for installation, maintenance, update and deinstallation of the product.
42. has to be created for each product individually.
43. needs WI 4.5 concerning to MS -> not for old Windows versions (min. Win XP SP 3) </li></ul>
44. Plans for the Future Idea:
45. Plans for the Future Installation process:
46. Plans for the Future Two kinds of installation: A B
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. Language independent : Java jar file contains all available localizations
49. Platform independent : Java jar file contains all informations about native installer processes
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. 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. Less upload, less redundancies (DLLs, ...).
53. More releases can be made available online.
54. Less download, because module and language selection happens before download starts.
55. QA concentrated on one installation set. </li></ul>
56. Plans for the Future Advantages: <ul><li>Simplified language handling, no language packs required. Only install maintenance mode.
57. Introduction of a Chainer, that supports micro-msi-packages also on older Windows systems.
58. msi databases separated like RPMs. Better modularization and easier development.
59. Micro-msi-packages can be in Pool process.
60. Unique installer appearance on all platforms, but using native installer. </li></ul>
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. Installation and Packaging - Presence and Future Dr. Ingo Schmidt-Rosbiegal [email_address]