> -----Original Message-----
> From: Nick Hibma [SMTP:nick.hi...@jrc.it]
> Sent: Monday, May 31, 1999 2:05 PM
> To: freebsd-po...@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 majord...@freebsd.org
> with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
