Date: Tue, 13 Apr 2004 13:30:01 +0000 From: Eivind Eklund <eivind@FreeBSD.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-ports@FreeBSD.org Subject: Re: Second "RFC" on pkg-data idea for ports Message-ID: <20040413133000.GE2625@FreeBSD.org> In-Reply-To: <p0602040cbca10a7dbe52@[128.113.24.47]> References: <p0602040cbca10a7dbe52@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
Please keep me in the Cc: list - I don't normally read ports@ On Mon, Apr 12, 2004 at 11:40:59PM -0400, Garance A Drosihn wrote: > The basic idea is to collapse many of the separate files for a > port into a single pkg-data file. The web pages explain why I > think this might be worth doing. Please check them out at: > > http://people.freebsd.org/~gad/PkgData/ There are two issues I immediately see (just to keep in mind during development): (1) The ability to do annotations and diffs on the patches themselves is fairly important. This ability can be kept even if they are assembled into a single file, but it requires that they are kept in a line-oriented format inside the assembled file. (2) If you do not use XML, you don't have to use a format that is "XML-like" - you can use e.g. significant indentation to make the format easier to read and edit. YAML (http://www.yaml.org) is an example of a markup format that is based on this, and gives much lighter (and thus easier to manually edit) markup. The ability to re-split the port into individual files for editing takes care of most other development issues, I think. Eivind.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040413133000.GE2625>