On Sun, Jan 30, 2005 at 12:28:53AM +0100, Santiago Vila wrote: > On Sun, 30 Jan 2005, Matthew Palmer wrote: > > > "Because I don't wanna play by the rules!" is not a rationale. > > You are mistaken. I want to play by the rules, but the rules say > executables should go to /usr/bin, *not* that everything in /usr/bin > should be executable. So if I say that you're a reasonable individual, that doesn't mean that you're *not* a fuckwit? Typically, in English, when you specify a certain criteria for something, you implicitly exclude anything not mentioned. Otherwise I'm going to recommend that we add /usr/include to the default path, since the FHS doesn't say I can't put executable commands there -- /usr/bin is only the "primary directory of executable commands", not the only directory, and /usr/include doesn't say you can't put commands in there. Or, alternately, we could read the FHS with our brains set to "reasonable interpretation" instead of "whatever-as-long-as-I-don't-have-to-do-any-work" and decide that gettext.sh belongs in /usr/share. > > 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. > > The same could be said for an executable called "ls". Exactly the same. Horseshit. If I do 'man ls' I can get the semantics for the ls command. No such benefit is provided me by gettext.sh. Hmm, time to report a bug against gettext-base for not having a manual page for gettext.sh... > The name "gettext.sh" should be distinctive enough to avoid namespace > pollution. Bwahahaha. It's the name of a common utility with '.sh' on the end. You don't think that *someone* isn't going to write a helper script called gettext.sh? > OTOH, if you are really worried about namespace pollution, > then please press the tab key twice while running bash. Aaaaand, your point being? - Matt
Attachment:
signature.asc
Description: Digital signature