Re: shell script sniplets in /usr/bin?
Goswin von Brederlow <firstname.lastname@example.org> writes:
> Matthew Palmer <email@example.com> writes:
>> On Sat, Jan 29, 2005 at 05:40:05PM +0100, Santiago Vila wrote:
>>> On Sat, 29 Jan 2005, Jochen Voss wrote:
>>> > [...]
>>> > My question: does anybody have further references for the question
>>> > whether it is ok or maybe even preferable to install non-programs in
>>> > /usr/bin?
>>> You forgot to quote last thing I said when closing the bug.
>>> So I'll repeat: Please read the logs for non-bug Bug#292759, where the
>>> author explains the rationale for putting gettext.sh in /usr/bin.
>> "Because I don't wanna play by the rules!" is not a rationale. So you have
>> to specify a path -- so what? The way things stand at the moment, if I were
>> to drop a gettext.sh in my ~/bin (which is quite likely, except that I don't
>> like to put a .sh on my helper scripts) your shell scripts would suddenly go
>> tits-up in a most unpleasant fashion. Personally, *that* would be enough to
>> make me want to hardcode the path.
>> - Matt
> That is why you normaly have ~/bin last in PATH.
Well, maybe I am not normal ;), but I put it first in PATH, with the
same rationale /usr/local/bin comes before /usr/bin (i.e. to be able
to override distribution supplied software with locally-installed
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | firstname.lastname@example.org
http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Any technology not indistinguishable from magic is insufficiently advanced.
-- Terry Pratchett