Date: 06 Apr 2000 18:28:31 -0700 From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) To: obrien@freebsd.org Cc: Nate Williams <nate@yogotech.com>, arch@freebsd.org Subject: Re: Import of tcsh into src/contrib/, replacing src/usr.bin/csh Message-ID: <vqc7leazolc.fsf@silvia.hip.berkeley.edu> In-Reply-To: "David O'Brien"'s message of "Thu, 6 Apr 2000 15:10:08 -0700" References: <20000406134916.A23265@dragon.nuxi.com> <200004062121.PAA24162@nomad.yogotech.com> <20000406144502.A25177@dragon.nuxi.com> <200004062150.PAA24400@nomad.yogotech.com> <20000406151008.B25607@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
First, let me mention that I *hate* csh and all its derivatives. I
have switched from tcsh to bash many years ago and honestly not proud
of being associated with a university who invented csh.
That said, I think it is a good idea to replace csh with tcsh. tcsh
and csh are so close, there is no issue on scripting (I am not aware
of any incompatibilities between tcsh and csh commands that will make
csh scripts fail), the only issue is whether we focus on the
additional size or the inconvenience of not having it there from the
beginning in single-user, fresh installations, etc. I don't think we
should penalize the majority of our users because of a few (embedded
systems people -- see below).
* From: "David O'Brien" <obrien@freebsd.org>
Now that Mike has shown up and made his obligatory comment to piss
off enough people it might be too late to save you, but anyway.... ;)
* Ok, then what about this:
*
* 1. Import tcsh into src/contrib/tcsh
* 2. copy src/bin/csh/Makefile to src/bin/csh/Makefile.csh
* 3. create src/bin/csh/Makefile.tcsh
* 4. src/bin/csh/Makefile looks like this:
*
* .if defined(WANT_OLD_CSH)
* .include ${.CURDIR}/Makefile.csh
* .else
* .include ${.CURDIR}/Makefile.tcsh
* .endif
I don't think that is necessary and needlessly bloats people's
/usr/src by having two copies of almost identical source.
My recommendation (as a Core-team member in charge of the ports
collection) would be to make csh a port, linked statically by default
with an option to install it in /bin, so embedded systems people who
need csh rather than tcsh to be on their systems can easily get it.
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqc7leazolc.fsf>