From owner-freebsd-ports  Mon Mar 10 05:21:41 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA19552
          for ports-outgoing; Mon, 10 Mar 1997 05:21:41 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA19532;
          Mon, 10 Mar 1997 05:21:38 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id FAA10131; Mon, 10 Mar 1997 05:16:55 -0800 (PST)
To: asami@vader.cs.berkeley.edu (Satoshi Asami)
cc: obrien@NUXI.com, ports@freebsd.org, current@freebsd.org
Subject: Re: Getting /usr/ports everywhere... 
In-reply-to: Your message of "Mon, 10 Mar 1997 03:54:18 PST."
             <199703101154.DAA01516@baloon.mimi.com> 
Date: Mon, 10 Mar 1997 05:16:53 -0800
Message-ID: <10128.857999813@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Thanks for committing it, but I don't think users can read
> /usr/ports/README while they are picking the distributions to install, 
> can they? :)

No, naturally not, but I'm hoping that at least some of them will
*read* the file before they start actually using /usr/ports. :-)

Even if I documented it at installation time it probably wouldn't do
much good since it's still a "35MB problem" then, and by the time it
becomes a "135MB problem" they're likely to have forgotten anything
they ever read in sysinstall. :-)

					Jordan