Re: dc and bc in Important?

1997-06-28 Thread Mark Baker
On Sat, 28 Jun 1997, Erik Andersen wrote: > iThis is correct, but has the unfortunate side effect of not being portable, > since not all /bin/sh happin to be bash. No, it also works with ksh. I believe posix.2 specifies that /bin/sh has to provide various features---basically to be a clone of k

Re: dc and bc in Important?

1997-06-28 Thread Erik Andersen
On Jun 28, Carey Evans wrote > [EMAIL PROTECTED] (Erik B. Andersen) writes: > > [snip] > > > For most math, expr works just fine. Of course, expr is limited > > to integer math, but it works and is portable. > > Actually, for integer math, bash or ksh works quite well. > > bash$ a=41 > bash$ l

Re: Policy wrt Important (was Re: dc and bc in Important?)

1997-06-28 Thread Kai Henningsen
[EMAIL PROTECTED] (John Goerzen) wrote on 25.06.97 in <[EMAIL PROTECTED]>: > By the current definition of Important: > * Sendmail should be there instead of smail since people expect >sendmail Nope. The sendmail interface should be there (fr example, /usr/lib/ sendmail), and it is provided

Re: dc and bc in Important?

1997-06-28 Thread Carey Evans
[EMAIL PROTECTED] (Erik B. Andersen) writes: [snip] > For most math, expr works just fine. Of course, expr is limited > to integer math, but it works and is portable. Actually, for integer math, bash or ksh works quite well. bash$ a=41 bash$ let a+=1 bash$ echo $a 42 -- Carey

Re: Policy wrt Important (was Re: dc and bc in Important?)

1997-06-28 Thread John Goerzen
Who said anything about "working"? Mark Eichin <[EMAIL PROTECTED]> writes: > > * gcc should be in Important because everybody expects a C compiler > > Maybe they expect it, but these days, they don't *get* one... none of > solaris, hpux, irix ship with a [working] C compiler... > -- John G

Re: dc and bc in Important?

1997-06-28 Thread Raul Miller

Re: Policy wrt Important (was Re: dc and bc in Important?)

1997-06-28 Thread Tim Sailer
In your email to me, Bill Mitchell, you wrote: > > > > On 25 Jun 1997, John Goerzen wrote: > > > By the current definition of Important: > >[...] > >sendmail > > * dpkg-dev should not be there since no experienced user of another > >Unix would expect it > > * lilo should not be there

Re: Policy wrt Important (was Re: dc and bc in Important?)

1997-06-28 Thread Bill Mitchell
On 25 Jun 1997, John Goerzen wrote: > By the current definition of Important: >[...] >sendmail > * dpkg-dev should not be there since no experienced user of another >Unix would expect it > * lilo should not be there because lilo is not part of UNIX I read it differently: ``Importan

Re: dc and bc in Important?

1997-06-28 Thread David Frey
On Wed, Jun 25 1997 8:35 PDT Bill Mitchell writes: > On Wed, 25 Jun 1997, David Frey wrote: > > Correlated note: It is not explicitely stated in the policy manual, but > > IMO we should flag all utilities mentioned in the POSIX.2 standard as > > 'Important' [...] > > IMHO, as long as t

Re: dc and bc in Important?

1997-06-27 Thread Erik B. Andersen
> > On Jun 23, John Goerzen wrote > > It seems to me that dc and bc aren't vital to the workings of a > > system (when I deselect them, dselect doesn't warn about any > > dependencies), yet they are in Important. Why? > > In addition to what everyone else has said about what "Important" > Really

Re: dc and bc in Important?

1997-06-27 Thread Raul Miller
On Jun 27, Erik B. Andersen wrote > For most math, expr works just fine. Of course, expr is limited > to integer math, but it works and is portable. Oops, you're right -- my biases are showing, sorry. [I make it a practice to never use expr.] -- Raul -- TO UNSUBSCRIBE FROM THIS MAILING LIST:

Re: Policy wrt Important (was Re: dc and bc in Important?)

1997-06-25 Thread Clint Adams
> "bare minimum" doesn't extend to a compilation environment. > or to printing, IMO. > > * netbase and netstd should both be there, they are standard > >on Unix It seems as though the implicit definition of "standard Unix system" omits a declaration of intended usage. -- TO UNSUBSCRIBE FR

Re: Policy wrt Important (was Re: dc and bc in Important?)

1997-06-25 Thread James Troup
John Goerzen <[EMAIL PROTECTED]> writes: > By the current definition of Important: > * Sendmail should be there instead of smail since people expect >sendmail People expect a mailer. Debian's default mailer is exim^H^H^H^Hsmail; that's a deliberate decision to override the commonly expected

Re: Policy wrt Important (was Re: dc and bc in Important?)

1997-06-25 Thread Mark Eichin
> * gcc should be in Important because everybody expects a C compiler Maybe they expect it, but these days, they don't *get* one... none of solaris, hpux, irix ship with a [working] C compiler... -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Tr

Re: Policy wrt Important (was Re: dc and bc in Important?)

1997-06-25 Thread Galen Hazelwood
John Goerzen wrote: > > OK, then I suspect the policy is at fault. (BTW, I checked it out and > I did find dc and bc on SunOS -- I had not known these programs were > on other OSs.) > > By the current definition of Important: [snip] > * lilo should not be there because lilo is not part of UNIX

Policy wrt Important (was Re: dc and bc in Important?)

1997-06-25 Thread John Goerzen
OK, then I suspect the policy is at fault. (BTW, I checked it out and I did find dc and bc on SunOS -- I had not known these programs were on other OSs.) By the current definition of Important: * Sendmail should be there instead of smail since people expect sendmail * dpkg-dev should not b

Re: dc and bc in Important?

1997-06-25 Thread Bill Mitchell
On Wed, 25 Jun 1997, David Frey wrote: [...] > > ``Important programs, including those which one would expect to find > > on any Unix-like system. If the expectation is that an experienced > > Unix person who found it missing would go `What the F*!@<+ is going > > on, where is foo', it should be

Re: dc and bc in Important?

1997-06-24 Thread David Frey
On Tue, Jun 24 1997 15:52 BST James Troup writes: > John Goerzen <[EMAIL PROTECTED]> writes: > > > It seems to me that dc and bc aren't vital to the workings of a > > system (when I deselect them, dselect doesn't warn about any > > dependencies), yet they are in Important. Why? > > Beca

Re: dc and bc in Important?

1997-06-24 Thread James Troup
John Goerzen <[EMAIL PROTECTED]> writes: > It seems to me that dc and bc aren't vital to the workings of a > system (when I deselect them, dselect doesn't warn about any > dependencies), yet they are in Important. Why? Because they match the first definition of Important in Policy (see below).

dc and bc in Important?

1997-06-23 Thread John Goerzen
It seems to me that dc and bc aren't vital to the workings of a system (when I deselect them, dselect doesn't warn about any dependencies), yet they are in Important. Why? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL P