cvs commit: CVSROOT modules ports/shells Makefile
ports/shells/bash3 Makefile distinfo pkg-deinstall pkg-descr
pkg-install pkg-plist ports/shells/bash3/files patch-ac patch-af
patch-bashline.c patch-builtins_shopt.def patch-config-bot.h ...
eikemeier at fillmore-labs.com
Thu Aug 12 05:39:47 PDT 2004
Garrett Wollman wrote:
> <<On Thu, 12 Aug 2004 00:33:52 +0200, Oliver Eikemeier
> <eikemeier at fillmore-labs.com> said:
>> Any reasons for that? Which means, do you actually use it? It conflicts
>> with the other bash ports, and the last release was 1996.
> Um, yes, I thought that was obvious. All of my shell universe is
I did a quick survey:
- OpenBSD removed bash1 ~ one year ago ("It smells funny.")
- NetBSD never had a bash 1.x port
- gentoo portage never had a bash 1.x port
(I didn't bother to check other OS distributions, although this might be
This means all of your shell universe is FreeBSD-based, which is not bad
by itself :).
I am aware of
but we have to have some procedure to get ride of old, unmaintained
ports. It is already marked broken on ia64, and there seem to be no
public security review any longer.
The point is: Is the bash1 port of public interest? Nothing hinders you
to copy the port to /usr/ports/local and keep using it, even when it is
deleted from CVS. Or better yet, assume maintainership and save it from
More information about the cvs-ports