"Inst" question
aether8203_at_yahoo.com
Date: 04/14/05
- Next message: Walther Mathieu: "Re: booting and installing OS in an Indy R5000"
- Previous message: Joerg Behrens: "Re: Octane"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 14 Apr 2005 13:54:06 -0700
Platform: IRIX 6.5.23
Background on us: Developing software with multiple builds, users, etc
When we install our formal baseline (aka an IDB package into a
directory path somwhere), we don't allow developers to alter it as we
have our testers validating the build. To accomodate the developers,
we came up with a "clone" process that basically is a bunch of LINKS to
the master so a developer can test out a new file without messing up
the master baseline. For example:
A Master Build would be:
/opt/BLD_40.10_F/
A clone would be:
/clone/My_test_build/ and all files under here point back to the files
under master.
Let's say I have a new executable, moo that I want to drop in place on
my clone. I can break the clone's link and drop it in place. So we go
from:
/clone/My_test_build/moo -> /opt/BLD_40.10_F/moo
to
/clone/My_test_build/moo (and of course all the other links are still
in place back to the main master).
That's great for one file here and there, but we package all our files
together into IDBs. This is then installed using "inst".
QUESTION: When you use "inst" to install onto your clone, how do you
not overwrite the master file (because the inst tool will follow the
link to the master) but rather, break the link in the clone and install
it there as I described above by hand?
Any ideas?
Thanks!
- Next message: Walther Mathieu: "Re: booting and installing OS in an Indy R5000"
- Previous message: Joerg Behrens: "Re: Octane"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|