From owner-freebsd-ports Fri Mar 7 05:50:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA12266 for ports-outgoing; Fri, 7 Mar 1997 05:50:13 -0800 (PST) Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA12258; Fri, 7 Mar 1997 05:50:09 -0800 (PST) From: garyj@frt.dec.com Received: from cssmuc.frt.dec.com by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV) id IAA23751; Fri, 7 Mar 1997 08:39:46 -0500 (EST) Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA20276; Fri, 7 Mar 1997 14:39:45 +0100 Message-Id: <9703071339.AA20276@cssmuc.frt.dec.com> X-Mailer: exmh version 1.6.4 10/10/95 To: ports@freebsd.org Cc: current@freebsd.org In-Reply-To: Message from "Jordan K. Hubbard" of Fri, 07 Mar 97 03:54:57 PST. Reply-To: gjennejohn@frt.dec.com Subject: Re: Getting /usr/ports everywhere... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Mar 97 14:39:45 +0100 X-Mts: smtp Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk jkh@time.cdrom.com writes: > I've been thinking about this for awhile, and I'm wondering whether or > not 2.2 might be a good time to unleash /usr/ports as a distribution > tarball as part of the release. > seems like a good idea to me. And this would help eliminate the "I grabbed this port from the server and can't get it to work. Oh BTW I'm running FBSD 1.0" :) I.e. trying to use ports for -current under an earlier version. --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) Gary.Jennejohn@munich.netsurf.de (play) gj@freebsd.org