>>"Raul" == Raul Miller <[EMAIL PROTECTED]> writes:
Raul> On Sun, Nov 05, 2000 at 02:48:18PM -0600, Manoj Srivastava wrote:
>> Would this not be easier done by having a mapping done at
>> unpack/install time, and then only scripts/programs with hard coded
>> paths need be changed?
Raul> Uh.. to the best of my knowledge, most packages which use these
Raul> paths "hard code" them in some file. Maybe you're suggesting
Raul> that, if we adopt this convention, programs could start using
Raul> this system (or something like it) at run time?
Really? I find I seldom have to use full path names for
binaries (I expect ls, grep, et al to be in the PATH, as they
should). I *NEVER* hard code the so called sbindir; and I think that
scripts should not, precisely for this reason.
If you need something that is not in the FHS PATH, I guess
calling a global config script is not unreasonable, _as an option_.
I am quite certain that installing in /opt or installing in
/some/path/that/I/control sohuld be a dpkg option, and certainly
should not bleed over into package maintainer scripts.
manoj
--
I have more hit points that you can possible imagine.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
