On Mer 27 avril 2005 16:08, Mathias Bauer a �crit : > M. Fioretti wrote: > >> Nobody (not me anyway) asked to use _one_ form of package. What is >> important is make sure that everything is always made available online >> in "source" form, that the distributors can pick and package their way >> for automatic installation and upgrade. *Without* extra work like >> dissecting a self-installing .sxw file to get the macro it wants to >> install by itself. > > Nobody should use sxw files for deployment. We use *UNO packages*. > > Their are zip files.
Can we hope to get too ? I know from experience Linux zip support is not on the level of the tar one (see also my naming remarks in previous messages) > They are installed using a command line tool that > is part of the office installation. This tool can be executed with user > or administrator (root) permissions and can deploy on a per user or on a > system wide base. It will not touch any files or settings in the office > installation or the user directory (and of course not anything else in > your system), it will only add some files in a defined place, a > subfolder of the "uno_packages" folder in either the "share" or the > "user" directory. Great. In that case the only thing we need to do rpm packaging is a way to specify an installation prefix (basically you tell your utility to install for the local OO.o installation, prepending a specific root. rpm then compresses the contents of this root, checksums and signs it. rpm invocation on the result unpacks this root contents on / on as many systems as you want.) This is a gross oversimplification, but gives you an idea of how rpm works Regards, -- Nicolas Mailhot --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
