Tim,
I could make them relocatable with a little extra effort; it is just a
matter of parsing the appropriate scripts. I have do actually grep
through every one of the appropriate file to see if they have a path
that needs changing, and this is flagged in the xml files produced by
the build. Now you can install them elsewhere but the software probable
wouldn't work.
If there is time I may make them relocatable.
Steve.
-----Original Message-----
From: Starlink development [mailto:[log in to unmask]] On Behalf Of
Tim Jenness
Sent: 28 April 2005 07:56
To: [log in to unmask]
Subject: Re: Starlink Nightly Build On System:RHEL-WS3-3_i386
On Tue, 26 Apr 2005, Rankin, SE (Stephen) wrote:
> Norman,
>
> Hadn't thought about that; yes the manifest should contain paths with
> the final installation location the user has chosen. For the binary
RPMS
> the installation location will be fixed but it could change for the
> source RPMS as they can be relocated.
>
Um. Why aren't the binary rpms relocatable? All the binary RPMs that Al
and I made 3 or 4 years ago were relocatable and for Starlink I would
assume that this is mandatory given the number of people that don't use
/star.
I know we have the hard-wired library paths now burnt into the binary
but:
1. Doesjn't LD_LIBRARY_PATH overcome that problem?
2. Surely there is a way to reburn a path?
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|