Re: Proposed new POSIX sh policy

2006-11-15 Thread David Weinehall
On Wed, Nov 15, 2006 at 10:05:47PM -0800, Thomas Bushnell BSG wrote: > On Wed, 2006-11-15 at 22:50 -0600, Manoj Srivastava wrote: > > I would rather get away from this wording totally. > > , > > | "Shell scripts specifying /bin/sh as interpreter must only use POSIX > > | features, add

Re: Proposed new POSIX sh policy

2006-11-15 Thread Thomas Bushnell BSG
On Wed, 2006-11-15 at 22:50 -0600, Manoj Srivastava wrote: > I would rather get away from this wording totally. > , > | "Shell scripts specifying /bin/sh as interpreter must only use POSIX > | features, additionally, they may assume that echo -n . Also, > | they may use test -a/

Re: Proposed new POSIX sh policy

2006-11-15 Thread Manoj Srivastava
On Wed, 15 Nov 2006 17:15:14 -0800, Russ Allbery <[EMAIL PROTECTED]> said: > Bruce Sass <[EMAIL PROTECTED]> writes: >> On Wed November 15 2006 16:45, Russ Allbery wrote: >>> No, but Policy currently requires scripts that use features not >>> available from POSIX to declare an appropriate shell,

Re: Proposed new POSIX sh policy

2006-11-15 Thread Manoj Srivastava
On Tue, 14 Nov 2006 20:03:54 +0100, Marco d'Itri <[EMAIL PROTECTED]> said: > On Nov 14, Manoj Srivastava <[EMAIL PROTECTED]> wrote: >> So, what features do we settle on? we can either standardize on, >> well, a standard: POSIX/SUSv3, -- but there are things we use that >> come from XSI. I guess

Re: Proposed new POSIX sh policy

2006-11-15 Thread David Weinehall
On Wed, Nov 15, 2006 at 10:46:51AM -0800, Russ Allbery wrote: > Bill Allombert <[EMAIL PROTECTED]> writes: > > > Hard-coding path is frowned upon theses days and there is no standard > > way to disable a shell built-in, so in practice we are actively > > prevented from using coreutils test and thu

Re: Proposed new POSIX sh policy

2006-11-15 Thread Russ Allbery
Bill Allombert <[EMAIL PROTECTED]> writes: > Hard-coding path is frowned upon theses days and there is no standard > way to disable a shell built-in, so in practice we are actively > prevented from using coreutils test and thus coreutils test features. So > the question is not merely what should b

Re: Proposed new POSIX sh policy

2006-11-15 Thread Thomas Bushnell BSG
On Wed, 2006-11-15 at 18:13 +0100, [EMAIL PROTECTED] wrote: > 1. /bin/sh can be a symbolic link to any shell. This can't be right. For example, it obviously can't be a link to /bin/csh. So since it can be a symbolic link to *some* shells and not others, telling maintainers "you know which ones w

Re: Proposed new POSIX sh policy

2006-11-15 Thread Matthias . Beier . Gronau
Hi, my starting point is: 1. /bin/sh can be a symbolic link to any shell. 2. The reasons to alter the symbolic link are legitimate. The rationale is: we do not want to cut off legitimate needs (even if we might not know them). The user consequently must have the freedom, to have /bin/sh as a sy

Re: Proposed new POSIX sh policy

2006-11-15 Thread Bill Allombert
On Wed, Nov 15, 2006 at 11:13:37AM +0100, Gabor Gombas wrote: > On Tue, Nov 14, 2006 at 09:36:36PM -0800, Thomas Bushnell BSG wrote: > > > Why? Surely it would be useful to know what the differences are between > > various shells. The statement "Posix-compatible" was apparently > > intended by t

Re: Proposed new POSIX sh policy

2006-11-15 Thread Gabor Gombas
On Tue, Nov 14, 2006 at 09:36:36PM -0800, Thomas Bushnell BSG wrote: > Why? Surely it would be useful to know what the differences are between > various shells. The statement "Posix-compatible" was apparently > intended by the authors of that part of the Policy Manual to do that > work for us, b

Re: Proposed new POSIX sh policy

2006-11-15 Thread Gabor Gombas
On Tue, Nov 14, 2006 at 06:13:34PM -0800, Thomas Bushnell BSG wrote: > I do. Debian test is provided by the coreutils package. As the man > page says: > >( EXPRESSION ) > EXPRESSION is true > > And, we have the existing rule in section 10.1 of the policy manual: > > "Two dif

Re: Proposed new POSIX sh policy

2006-11-15 Thread Andreas Barth
* Thomas Bushnell BSG ([EMAIL PROTECTED]) [061115 07:31]: > On Tue, 2006-11-14 at 22:15 -0800, Russ Allbery wrote: > > > The problem sparking this thread and my initial work on a Policy patch is > > not a problem caused by shells with builtins; it is, in fact, not a > > technical problem at all in

Re: deluser on purge (was: Piuparts testing status update)

2006-11-15 Thread Andreas Barth
* Russ Allbery ([EMAIL PROTECTED]) [061115 03:12]: > Steve Langasek <[EMAIL PROTECTED]> writes: > > On Tue, Nov 14, 2006 at 09:35:12PM +0100, Frank Lichtenheld wrote: > > >> Hmm, I would read policy in a way that since a package can not rely on > >> its dependencies being present during purge, the

Re: deluser on purge (was: Piuparts testing status update)

2006-11-15 Thread Loïc Minier
On Tue, Nov 14, 2006, Steve Langasek wrote: > > This is something that I'd really like to see us sort out in policy, since > > I think we should be able to describe consistent behavior with regard to > > system users and package purging to our users. Right now, every > > maintainer is making their