From owner-freebsd-ports Thu Apr 13 16:28:26 2000 Delivered-To: freebsd-ports@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 931D737BC2E for ; Thu, 13 Apr 2000 16:28:23 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 12ft1t-000PA2-00; Fri, 14 Apr 2000 01:28:09 +0200 Date: Fri, 14 Apr 2000 01:28:09 +0200 From: Neil Blakey-Milner To: Robert Withrow Cc: Brandon Fosdick , ports@FreeBSD.ORG Subject: Re: Some new ports broken on 4.0REL Message-ID: <20000414012809.A96692@mithrandr.moria.org> References: <200004132322.TAA36744@tuva.engeast.baynetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004132322.TAA36744@tuva.engeast.baynetworks.com>; from bwithrow@nortelnetworks.com on Thu, Apr 13, 2000 at 07:22:03PM -0400 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ lots of arb crap removed ] > Instead, I think the ports system should start off with just the > infrastructure: the INDEX, the Mk directory (and maybe the Templates > directory) and individual ports should be pulled from the distribution > sites (or the cdrom) using something like pib or portcheckout. These > tools should also provide a means for updating the INDEX file and for > updating individual ports. Neither of these tools (and no tools that > I am aware of) do all of this. I was just trying to help, I really don't need your long essay on the lack of documentation and functionality that you'd really like. However, your infrastructure sounds nice. When can I expect the code? Where are your patches to fix the documentation, while you're at it? Neil -- Neil Blakey-Milner Hacker In Chief, Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message