cvs commit: CVSROOT modules ports/shells Makefile pkg-installpatch-bashline.c patch-builtins_shopt.def patch-config-bot.h ...

[Garance A Drosihn]

At 12:33 AM +0200 8/12/04, Oliver Eikemeier wrote:
>Garrett Wollman wrote:
>
>><<On Wed, 11 Aug 2004 18:11:52 +0200, Oliver Eikemeier 
>><eikemeier at fillmore-labs.com> said:
>>
>>>a good idea, just do it. I'm fine with deleting bash1, but I
>>>think we should keep bash2 around a little longer, unfortunately
>>>the bugs in the .0 release seem not to be purely hypothetical
>>
>>I would miss bash1.  (Not that I'm volunteering to maintain it
>>or anything.)
>
>Any reasons for that? Which means, do you actually use it? It
>conflicts with the other bash ports, and the last release was 1996.

It is useful if you have a lot of bash1 scripts and rc files,
and you don't have time "right now" to figure out why various
obscure things will stop working.  I will admit that I do not
use it any more, but I was happily using it up to about 2002.
I would like to thank the people who kept it around that long.

It might be nice to have it install as 'bash1' instead of 'bash',
though, just to avoid the conflicts.

In a different message on Aug 11th, Doug Barton wrote:
>someone else wrote:
>>
>>The jury is still out on if 'bash2' needs to exist for a while.
>>We should probably have a plain 'bash' port that is the latest
>>version.
>
>I disagree with this, and I share David's frustration that this
>action was rushed into without proper discussion. ...
>
>Finally, as a devoted bash2 user, I don't plan to switch to bash3
>until it's proven stable. I'm also sure that there are numerous
>FreeBSD sites who will continue to need a bash2 port for the
>forseeable future. ...

I strongly agree with Doug's comments here.

-- 
Garance Alistair Drosehn            =   gad at gilead.netel.rpi.edu
Senior Systems Programmer           or  gad at freebsd.org
Rensselaer Polytechnic Institute    or  drosih at rpi.edu