From owner-freebsd-arch Thu Apr 6 18:29:35 2000 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 2D9A037B9D0 for ; Thu, 6 Apr 2000 18:29:29 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id DAA12493 for ; Fri, 7 Apr 2000 03:33:02 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA34761 for freebsd-arch@freebsd.org; Fri, 7 Apr 2000 03:29:26 +0200 (CEST) Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 139D337BFFA; Thu, 6 Apr 2000 18:28:47 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca5-83.ix.netcom.com [209.109.234.83]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA06274; Thu, 6 Apr 2000 21:28:35 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id SAA86912; Thu, 6 Apr 2000 18:28:32 -0700 (PDT) To: obrien@freebsd.org Cc: Nate Williams , arch@freebsd.org Subject: Re: Import of tcsh into src/contrib/, replacing src/usr.bin/csh 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> From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 06 Apr 2000 18:28:31 -0700 In-Reply-To: "David O'Brien"'s message of "Thu, 6 Apr 2000 15:10:08 -0700" Message-ID: Lines: 40 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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" 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