Thanks for all the great suggestions folks. Unfortunately symlinking won't work in our case. Part of the difficulty we run into is the directories that are backed up are different for the various servers. And the backpack won't follow symlinks. At this point our best idea is to create a newuser on all servers and then install openpkg into it's home directory for example: /export/home/newuser/openpkg. We can then make a general group that everyone is in so they can use the openpkg install. I think this is our best option at this point.
BTW, incase anyone was wondering the binary compiled RPM packages are also tied to the directory structure that was created by the original bootstrap. So basically unless you always keep the same directory structure like /openpkg the binary rpm packages are useless. Found this out based on the perl binary rpm. It's possible some may work but I'm sure there are a lot that won't. Thanks again, John On 10/29/07, Douglas S. Summers <[EMAIL PROTECTED]> wrote: > > J P wrote: > > Hey All, > > > > We are trying to use openpkg as an updated deployment of the archaic > > software that normally comes with solaris 9. The biggest part we are > > interested in are the perl libraries. We have gotten it installed on a > > test server. But we've noticed that once the installation is setup > > everything appears to be hard-coded to that directory structure. For > > example if I installed it in /export/home/tambu/openpkg and then I "mv > > /export/home/tambu/openpkg /openpkg" when I try to do something like > > "perl -e use Email::MIME::Encodings" it fails because perl is hard-coded > > to use the /export/home/tambu/openpkg for it's libraries. Now I realize > > that we could add the new director to the PERL library but we wanted to > > find out if there is a better way. > > > > After playing with the openpkg installation script > > "openpkg-20071019-20071019.sparc64-solaris9-openpkg.sh > > <http://openpkg-20071019-20071019.sparc64-solaris9-openpkg.sh>" it > > appears that the USERNAME, GROUP, and PREFIX PATH that was used to > > compile the script is hardcoded in 100's of places in the file so that > > we cannot reuse it easily. Our current thought is that we will recompile > > two copies of the installation script with the proper user/group/path, > > The reason we need two is that the servers it's being deployed to have > > very strict security restrictions and we don't have similar users or > > directories on both servers. > > > > My question is that once we create a "unique" installation script for > > each set of servers will we be able to safely reuse the same binary RPM > > files that were originally created under the /export/home/tambu/openpkg > > directory? Or do we have to recompile everything including all the perl > > modules? > > > > Thanks for your assistance. > > > > Tambu > > I would recommend doing the following: > > 1) Build OpenPKG under /openpkg, but make /openpkg a symlink to > somewhere else. That way you can move the real location if necessary and > just fix the symlink as needed. > > 2) Always specify the user/group during the bootstrap build. That way > you will have consistent UID/GID pairs on every platform. > ______________________________________________________________________ > OpenPKG http://openpkg.org > User Communication List openpkg-users@openpkg.org >
