Hi Stephan,

Stephan Bergmann schrieb:

Can you think of any other (dis-)advantages of the two approaches?

To stress the disadvantage of the one-tree approach: multiple packages for a single binary also need multiple (security-) patches.

A few words on prefixes: we currently use /opt/openoffice.org2.2 as relocatable part of the packages, while usual prefixes (at least on Solaris) are "/opt" or "/" or "/usr".

For admins actually making use of relocations regulary, it is quite likely that (s)he initially ends up with e.g. /usr/local/program etc. when trying to relocate to /usr/local.

While writing the above, another thought just came to my mind: if we would adjust the structure of OOo to fit nicely into "/usr" or "/", we could easily transform unbundled packages to bundled ones and vice versa, even at install time !

So if we would use "/usr" or "/" (or even "/opt") as prefix/basedir for all packages and provide a script or gui tools that makes it easy for the user to relocate all packages to e.g. "/opt/openoffice.org2" the result (again) would be a single tree, but without the disadvantage of having multiple packages.

We would still need to fix all those places that can not deal with the new default prefix though.

Are there any constraints imposed by additional package formats (e.g., even if it were a brittle solution, is it theoretically possible to relocate packages a la rpm --prefix for package formats like non-rpm Linux or Mac OS X, or would those be show stoppers anyway)?

IIRC Debian packages support alternate root, but not changing prefixes. Not sure about slackware tgz's.

Also I haven't checked whether automated installation methods like Solaris Jumpstart, RedHat Kickstart etc. allow to specify non default prefixes.

Regards,
Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to