From owner-freebsd-ports  Mon May 31  5:20:36 1999
Delivered-To: freebsd-ports@freebsd.org
Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0C69C152CA; Mon, 31 May 1999 05:20:31 -0700 (PDT)
	(envelope-from mladavac@metropolitan.at)
Received: by TITAN with Internet Mail Service (5.0.1458.49)
	id <LNJ062W7>; Mon, 31 May 1999 14:23:13 +0200
Message-ID: <55586E7391ACD211B9730000C110027617962F@r-lmh-wi-100.corpnet.at>
From: Ladavac Marino <mladavac@metropolitan.at>
To: 'Nick Hibma' <nick.hibma@jrc.it>, freebsd-ports@FreeBSD.ORG,
	freebsd-hackers@FreeBSD.ORG
Subject: RE: a two-level port system?  (fwd)
Date: Mon, 31 May 1999 14:18:01 +0200
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: text/plain
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> -----Original Message-----
> From:	Nick Hibma [SMTP:nick.hibma@jrc.it]
> Sent:	Monday, May 31, 1999 2:05 PM
> To:	freebsd-ports@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG
> Subject:	Re: a two-level port system?  (fwd)
> 
>  > 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
> 
	[ML]  Well, I'll try to make a proof of concept tonight with a
flatfile database not unlike the normal diff over several files.  The
result will be an ascii file which you could diff against and transfer
only the diffs.

	Basically the format will be
	graphics
	graphics/gimp
	graphics/gimp/Makefile
	<blank><line 1 of makefile>
	<you get the idea>

	It will be trivial to expand it into directories in order to
build ports, and compact directories into the file once the port has
been added/updated.

	Advantages:
	1) the file behaves like any other source file as far as CVS and
CVSup is concerned: one stores and transfers diffs only
	2) shar does it (and this will not be much different)
	3) well, it is ascii :)

	/Marino
> IMHO we'd end with something as silly as an OO database.
> 
> Nick
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message