Hi Pavel, I tried to install from the 1.9.81 .deb packages, and met some minor problems.
To start with, the old 1.1.3 OOo version was not removed. Which was good, since nothing was installed, too. Curious about the reasons, I took a look on the packages themselves, and noticed the following (I'm not a .deb guru at all, and surely have missed a lot of things): Dependencies: Most of the packages depended on the core01 package - and only on it. I doubt that this is the real situation - at least, core01 should have depended on the other core packages, if they are ever needed. Also, the language pack depends on no other package (and I don't believe it is of much use just by itself). Package internals: While the packages appeared to be created in a proper way (with the dpkg-dev tools), they missed most of the info they would need to work. I noticed the following problems, listed by .deb control files: control: This is the main control file of a debian package. Mandatory. In these packages, it is present, but misses most of the needed fields. Any control file from a Debian OOo 1.1.3 deb package would be a good example what must be written in here. conffiles: Expected to contain a list of the OOo global configuration files (these that are installed by this package). Currently empty (does OOo 2.0 packages install config files at all? ;-) shlibs: Expected to contain a list of the shared libs installed by the package. Not present in any of the packages I looked in. Theoretically not needed, if OOo doesn't install any shared libs; I have the feeling, however, that it does. preinst: Usually a shell script. Expected to prepare the things for the unpacking of the archive tree and files (eg. create needed dirs, backup important stuff etc.) Optional, but typically needed. Currently missing. postinst: Usually a shell script. Expected to do homework after the system is unpacked (eg. start a daemon after installing it). Appears to be intended for RPMs, not DEBs - that is, it will not work correctly here. prerm: Usually a shell script. Expected to prepare the system for being removed (eg. to stop a daemon before removing it). Optional, but typically needed. Currently missing. postrm: Usually a shell script. Expected to do cleanup after the package contents is deleted. Appears to be intended for RPMs, not DEBs... md5sums: A file, listing the MD5 sums for the files to be installed. Optional, but typically a good idea. Currently missing. config: Usually a shell/Perl/Python script. Asks the user questions over the installation details before performing it (sometimes called a preconfiguration). Needed if some details should better be asked to the user. Currently missing. Typically, a deb package header may contain other needed files, too - templates, etc. ANother note: The Debian versions of OOo typically contain a package called openoffice.org-debian-files, which contains all possible differencies between a Debian OOo and any other OOo. Typically, the scripts numbered above would contain references to utilities and procedures inside this package - see the typical Debian OOo package scripts for examples. Some of the things inside this package may be obsolete, but some will probably be needed. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
