From owner-freebsd-hackers  Thu May 23 04:27:19 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA03891
          for hackers-outgoing; Thu, 23 May 1996 04:27:19 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA03881;
          Thu, 23 May 1996 04:27:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id EAA03396; Thu, 23 May 1996 04:27:00 -0700 (PDT)
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: sos@FreeBSD.org, gpalmer@FreeBSD.org, hackers@FreeBSD.org,
        peter@FreeBSD.org
Subject: Re: src/gnu 
In-reply-to: Your message of "Thu, 23 May 1996 13:00:25 +0930."
             <199605230330.NAA06882@genesis.atrad.adelaide.edu.au> 
Date: Thu, 23 May 1996 04:27:00 -0700
Message-ID: <3393.832850820@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> If it's kept as a 'port' rather than mutilated and stuffed into the source
> tree, it should _theoretically_ be easier to get the FSF people to accept
> patches to it.  I think the idea has a lot of merit.

One plus is that with the ports collection model (and it's funny that
I never thought of anything outside of /usr/ports including
bsd.port.mk before, but thinking about it now it makes perfect sense :-),
all the patches will always be broken out in ONE location and
it becomes a very simple exercise to work with the FSF until your
patches directory goes away - what other metric could be simpler?

I'm not sure that having gcc bmake'd has ever bought us much anyway.
Same goes for groff, for that matter.

					Jordan