Re: Bug#292759: shell script sniplets in /usr/bin?

2005-02-01 Thread Joel Aelwyn
[ Removing the Cc for the bug, adding -policy, and setting M-F-T, as this ] [ is really a policy question.] On Mon, Jan 31, 2005 at 11:45:57AM -0500, Joey Hess wrote: Matthew Palmer wrote: If I do 'man ls' I can get the semantics for the ls command.

Re: Bug#292759: shell script sniplets in /usr/bin?

2005-01-31 Thread Santiago Vila
On Mon, 31 Jan 2005, Martin Schulze wrote: Adrian von Bidder wrote: You wouldn't need to change every script - you just need to move gettext.sh to /usr/share/gettext/scripts and create /usr/bin/gettext.sh with the content Sean suggested. Which buys us what? This new gettext.sh

Re: Bug#292759: shell script sniplets in /usr/bin?

2005-01-31 Thread Joey Hess
Matthew Palmer wrote: 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... I realize that you're probaly using that example as a rhetorical

Re: Bug#292759: shell script sniplets in /usr/bin?

2005-01-31 Thread Lars Wirzenius
ma, 2005-01-31 kello 14:24 +1000, Anthony Towns kirjoitti: Dude, PATH is for programs; gettext.sh is a shell library. It doesn't really matter that . happens to search PATH for shell libraries -- unless they also happen to be binaries, PATH is just not an appropriate place for libraries.

Re: Bug#292759: shell script sniplets in /usr/bin?

2005-01-31 Thread Lars Wirzenius
ma, 2005-01-31 kello 13:21 +0200, Lars Wirzenius kirjoitti: ma, 2005-01-31 kello 14:24 +1000, Anthony Towns kirjoitti: Dude, PATH is for programs; gettext.sh is a shell library. It doesn't really matter that . happens to search PATH for shell libraries -- unless they also happen to be

Re: Bug#292759: shell script sniplets in /usr/bin?

2005-01-30 Thread Anthony Towns
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. It also says that

Re: Bug#292759: shell script sniplets in /usr/bin?

2005-01-29 Thread Santiago Vila
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 you have to specify a path --

Re: Bug#292759: shell script sniplets in /usr/bin?

2005-01-29 Thread Matthew Palmer
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