From owner-freebsd-current Wed Jun 19 12:02:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09360 for current-outgoing; Wed, 19 Jun 1996 12:02:45 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA09342; Wed, 19 Jun 1996 12:02:33 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA13628; Wed, 19 Jun 1996 11:56:08 -0700 From: Terry Lambert Message-Id: <199606191856.LAA13628@phaeton.artisoft.com> Subject: Re: tcl -- what's going on here. To: nate@sri.MT.net (Nate Williams) Date: Wed, 19 Jun 1996 11:56:08 -0700 (MST) Cc: jmb@freefall.freebsd.org, jkh@time.cdrom.com, nate@sri.MT.net, phk@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199606191656.KAA06240@rocky.sri.MT.net> from "Nate Williams" at Jun 19, 96 10:56:31 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > We're trying to *avoid* adding GPL'd components to the tree, and if we > use Gmake we make the tree unusable for anyone trying to use FreeBSD for > 'other' purposes, which is one of the tenets ofthe BSD vs. GPL licensing > scheme. Actually, this is a false-cause argument, since the GCC that is supposed to be "bmake'd" is itself GPL. The argument, however, *does* carry significant weight with regard to non-GPL code that required GNU tools to make it function. I think it is possible to subdivide the policy problem; however, under no circumstances can I see how it would be beneficial to import code in such a way as to prevent local delta's from being applied to a vendor branch. The "uuencoded tarball" method strikes me as singularly unpleasent. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.