Date: Wed, 14 Apr 2004 16:15:51 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: dirk.meyer@dinoex.sub.org (Dirk Meyer), freebsd-ports@freebsd.org Subject: Re: Second "RFC" on pkg-data idea for ports Message-ID: <p06020406bca34a92ceb6@[128.113.24.47]> In-Reply-To: <jGY1%2Bv7vdg@dmeyer.dinoex.sub.org> References: <20040413121925.GB29867@voodoo.oberon.net> <p0602040cbca10a7dbe52@[128.113.24.47]> <20040413121925.GB29867@voodoo.oberon.net> <p0602041abca1e49dde40@[128.113.24.47]> <jGY1%2Bv7vdg@dmeyer.dinoex.sub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 1:33 PM +0200 4/14/04, Dirk Meyer wrote:
>Garance A Drosihn schrieb:,
>
>> I wasn't looking for XML per se, so much as just something that
>> would be easy for a program to process. This should allow for
>> pretty arbitrary text for the values of each section, in the
>> same way that the present plain-files would accept anything.
>> No need for \'s to escape double-quote characters, or worries
>> about embedded ${} or any other characters which might be
>> special to make or to /bin/sh.
>
>A Makefile is very easy to process.
>We have all the tools for this.
I noticed how easy it was when the pkg-comment -> COMMENT
change broke the ports tree. That's exactly what got me
thinking about this project in the first place.
I'm sorry, but I really don't think it's the right format for
storing and manipulating arbitrary data. Yes, you can pound
any value into make variables if you hammer hard enough, but
for some kinds of (arbitrary) data I (personally) think it's
too much effort for too little reward.
--
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06020406bca34a92ceb6>