>
> Currently, I store all package information in a large XML
> document which I update by hand whenever a new package is
> ITPd, an existing package is updated, or some other change
> must be made against the live repository. XSL transformations
> convert this XML document into several other formats,
> including the plaintext PPL, MPL, and make files to automate
> downloading, reviewing, and pushing packages into the live repository.
>
If all backend processing is xml-based and all setup.hint files have to
be modified why to not switch the format of setup.hint (and perhaps
setup.ini) files to xml also? The only disadvantage I see is that
current setup.hint format is human-readable, xml is hard to read for
both human and computer:-)
<package name="libfoo" version="0.01" release="1">
<sdesc "The Finite Object Organization library"/>
<ldesc "The Finite Object Organization library provides service
routines to organize finite objects."/>
<category "Libs"/>
<requires>
<need "prefoo"/>
<need "cygwin"/>
</requires>
<maintainer "Daniel Reed"/>
<related-to foomaster/>
<location>
<bin-url
"http://www.example.net/products/foomaster/Cygwin/libfoo-%{version}-%{re
lease}.tar.bz2"/>
<src-url
"http://www.example.net/products/foomaster/Cygwin/libfoo-%{version}-%{re
lease}-src.tar.bz2"/>
<hint-url
"http://www.example.net/products/foomaster/Cygwin/libfoo.hint"/>
</location>
<build>
<configure "--disable-coolstuff --with-prefoo
--prefix=/usr"/>
</build>
</package>
Sergey Okhapkin
Somerset, NJ
