From owner-cvs-all Wed Nov 15 11:17:17 2000 Delivered-To: cvs-all@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 7E4FF37B4C5; Wed, 15 Nov 2000 11:17:12 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id IAA28629; Thu, 16 Nov 2000 08:17:10 +1300 (NZDT) Message-Id: <200011151917.IAA28629@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Date: Thu, 16 Nov 2000 08:17:47 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Adding all of the source tree into FreshPorts Reply-To: dan@langille.org X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After success with FreshPorts, it's to move on to the rest of the source tree. The major difference between the ports tree and the source tree is that the source tree solution must contend with versions (-release, - stable, -current). I'd like to start discussing the design with interested parties. Initially, here, and later moving to the develop@freshports.org mailing list. In short, by adding cvs-all to FreshPorts, it will allow people to watch a particular file or a sub-tree. They would be notified when any change occurs to that file or any file with their watched sub-tree. First: is this an appropriate venue for initial discussions? This message was originated posted to cvs-all on 9 November. There was no response, so in the hopes that it was merely misseed by those who might possibly be interested, I'm posting it again, and this time including cvs-committers@FreeBSD.ORG. cheers -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ FreshPorts - http://freshports.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message