From owner-freebsd-ports Mon May 31 5: 5:31 1999 Delivered-To: freebsd-ports@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 2E4F514E66; Mon, 31 May 1999 05:05:25 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id OAA03056; Mon, 31 May 1999 14:05:21 +0200 (MET DST) Date: Mon, 31 May 1999 14:05:20 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: freebsd-ports@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: a two-level port system? (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Moving these files to ftp requires good automatic means to keep > > ftp servers updated. However as of today there are no such means > > available. > > > > CVSup is definitely easiest way to keep well defined collection > > of files up to date. > > Folks, how about _admitting_ finally that our ports collection is a > database? We wouldn't need anything else than standard system tools to > maintain a ports.db file containing all that we want as DB records. Some thoughts: 1) Cvsupping the while database on every change or writing YAT (Yet Another Tool) to do this properly 2) Keeping things like Makefiles, descriptions, patches in a database 3) making it a binary file instead of Human Readable ASCII IMHO we'd end with something as silly as an OO database. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message