Stephane ENTEN ([EMAIL PROTECTED]) said:
> I recently upgraded my groff package with the latest (1.15-2)
> and discovered that the groff binary wasn't included anymore.
>
> Has it been splitted into another package NOT named like
> *groff* ?
>
> I doubt since an rpm -qpl *.rpm | grep bin/groff
>
> Maybe a env var to make it totally backwards even w/o warning?
> $I_WANT_A_BROKEN_BASH perhaps, because why should ps have all the fun? :)
Wotta thought. I like it.
A bash front end (stored as /bin/bash) that execs the good bash or the old
stuffed up one.
>
--
Cheers
John Summerfiel
Hi,
I recently upgraded my groff package with the latest (1.15-2)
and discovered that the groff binary wasn't included anymore.
Has it been splitted into another package NOT named like
*groff* ?
I doubt since an rpm -qpl *.rpm | grep bin/groff
in my (up to date) RPM repository returns nothing
> To: [EMAIL PROTECTED]
> Subject: Re: bash2
> Date: Wed, 02 Feb 2000 07:08:18 +0800
> From: John Summerfield <[EMAIL PROTECTED]>
>
>
> >
> > perhaps a simple bash2 script to update bash1 scripts?
>
> I suspect it's not so simple. While I only found two problems here, I'm
> sure there are more
>
> perhaps a simple bash2 script to update bash1 scripts?
I suspect it's not so simple. While I only found two problems here, I'm
sure there are more. An option to bash (maybe --syntax to do a syntax
check, no more) would have been a good thing.
It would have been nice to be able to check e
