On Ven 13 mai 2005 14:19, J�rgen Schmidt a �crit : > Nicolas Mailhot wrote: >> On Ven 13 mai 2005 12:36, M. Fioretti a �crit : >> >> My (admitedly weak) understanding of how the whole thing should work is >> : >> >> 1. have the uno package source in an archive (archive type and layout >> needs to be specified to be rpm/deb friendly - rpm for example can >> digest >> almost everything but some formats are much easier than others.) >> >> 2. at the native package build time, run the oo.o package utility to put >> things in the right place (needs the buildroot prefix thing I've written >> about) >> >> 3. the native package install stage is then just extracting these files >> on >> the same place on the target system >> >> So you only need the oo.o packaging utility at build time, and IMHO for >> stuff like clipart and templetes that's not OO.o specific you should not >> even need it there. > > it's not so easy and unopkg does a little bit more during installation > of UNO packages.
What more does unopkg do during installation ? I thought it would not modify any file not part of the uno package. -- Nicolas Mailhot --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
