Peter Tribble wrote:
> One way it works in Solaris is that you go > > pkgadd -R /usr/local > > and all the files get /usr/local stuck on the front - both the installed > files and all the packaging stuff. So you would end up with something > silly like /usr/local/usr/bin/ssh, and you would have to make sure that > the files you installed would actually work relocated like that. (The > normal use for this is something like a diskless client where the relocated > path gets mapped back to / on the client.) Using alternate root relocation to do arbitrary relocation is usually hit-or-miss. The path you specify with -R is interpreted by the pkg tools as being an alternate OS instance, which /usr/local is not (e.g. it doesn't have a var/sadm structure, or etc/vfstab, which the package tools rely on in many cases). But it's the only way to relocate the pkgdb in the way that RPM's --root does. RPM's --root does behave very similarly to pkgadd's -R, in that in most cases installation of an RPM into an arbitrary root will usually fail because it won't be able to find <root>/bin/sh, showing that it too assumes the --root value is pointing to an alternate *OS instance*. -jhf-
