From owner-freebsd-current Wed Dec 17 21:39:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA20010 for current-outgoing; Wed, 17 Dec 1997 21:39:43 -0800 (PST) (envelope-from owner-freebsd-current) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA18919 for ; Wed, 17 Dec 1997 21:18:34 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.5) id VAA00499; Wed, 17 Dec 1997 21:20:30 -0800 (PST) From: Steve Kargl Message-Id: <199712180520.VAA00499@troutmask.apl.washington.edu> Subject: Re: why is tcl in base distribution In-Reply-To: <2939.882411127@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 17, 97 06:12:07 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 17 Dec 1997 21:20:29 -0800 (PST) Cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Jordan K. Hubbard: > > I agree with this Very Smart Idea. Tcl belongs in the ports collection. > > Period. > > If you resurrect this flame war 2 weeks before Christmas, Steve, > I shall personally fly out to wherever you live and kill you. :-) Well, I did say I live in Seattle. > Believe me, this has been discussed to *death* (Satoshi wasn't kidding > when he said there was a 1.6MB archive of mail available if anyone > wanted to read it) and all we proved was that it was an issue which > cost far more time and effort to *discuss* than it did to simply live > with for now and see how the situation develops further. Resurrecting I'm well aware of the history having followed the mailing lists/newgroups since 386BSD+patchkit days. If you ignore a problem, it doesn't go away. This is similar to Uncle Ernie, the family drunk. As along as he drinks somewhere else, it's not your problem. > All of us are also painfully aware of the vaporware status of the > freebsd admin tools and it's been a long-standing thorn in the side > for several of us. I first tried to do this work alone and, not > surprisingly, it didn't happen. Then I called for volunteers on it > (where were you, Steve? :) and, not surprisingly, that didn't work I've sent in PR's. Mostly correction to the documentation. The one time I tried to improve a tool, my submission was beaten into the ground. If you recall, I modified install(1) to take a -z and/or -Z argument to compress files during an install. Bruce or Garrett (if I remember correctly) added the -C option as a result (among others). I've also considered stripping everything out of sysinstall that is not necessary for preparing a new hard drive for use. The utility was going to be named newdisk. However, sysinstall has been a moving target. Merry Christmas, Jordan. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html