Re: Bug#148172: command -v in postinsts violating policy

2002-05-25 Thread Joey Hess
Luca - De Whiskey's - De Vitis wrote: The same goal can be achived with other commands or shell builtin. Such as? -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bug#148172: command -v in postinsts violating policy

2002-05-25 Thread Clint Adams
Such as? test -x /usr/sbin/install-docs || echo hi ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bug#148172: command -v in postinsts violating policy

2002-05-25 Thread Clint Adams
That's different and more fragile: it relies on a fixed path which command -v does not. Is this important in the event that install-docs gets moved, or so that someone can put a different install-docs in the PATH? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.

Re: Bug#148172: command -v in postinsts violating policy

2002-05-25 Thread Joey Hess
Clint Adams wrote: Such as? test -x /usr/sbin/install-docs || echo hi Personally, the only such paths I ever hard code are /etc, #!/bin/sh, and #!/usr/bin/perl, and I've been thinking about using the env trick for that last. ess hardcoded paths is good for flexability, and avoid possible

Re: Bug#148172: command -v in postinsts violating policy

2002-05-25 Thread David Schleef
On Sat, May 25, 2002 at 09:39:28PM -0400, Joey Hess wrote: Clint Adams wrote: Such as? test -x /usr/sbin/install-docs || echo hi Personally, the only such paths I ever hard code are /etc, #!/bin/sh, and #!/usr/bin/perl, and I've been thinking about using the env trick for that last.