Re: package.xml DTD 1.1 avaible

On 4 Sep 2003 at 12:33, Tomas V.V.Cox wrote: > On Thursday, September 4, 2003 10:43, Stefan Neufeind wrote: > > > On 4 Sep 2003 at 1:10, Tomas V.V.Cox wrote: > > >> On Thursday, September 4, 2003 0:42, Stefan Neufeind wrote: > >> > >> > On 3 Sep 2003 at 14:22, Tomas V.V.Cox wrote: > >> > >> >> I've done an big update/fix/complete of the current DTD 1.0. The > >> >> main purpose of it, is to support all the new features added in > >> >> the recent months and to be more strict on the pacakge.xml > >> >> format. > >> >> > >> >> Almost none (if any) pacakge.xml file under the PEAR CVS > >> >> conforms the new DTD (mostly because of the new required element > >> >> order). Please review and test it (you can use the xmllint > >> >> --dtdvalid command shipped with libxml2 or my DTD class), > >> >> because I'd like to add DTD validation into "pear > >> >> package-validate" and perhaps in the future to comply with the > >> >> DTD, could become a requirement (both at the pear-cmd and the > >> >> web). > >> >> > >> >> You can find the new dtd at: > >> >> > >> >> http://pear.php.net/dtd/package.1.1.dtd > >> >> > >> >> (is not yet a public url) > >> > >> > And it doesn't even appear to be "public" for us :-) Could you > >> > check the url again, please? > >> > >> The correct url is actually: > >> > >> http://pear.php.net/dtd/package-1.1.dtd > > > Tomas, > > > testing your dtd against a package.xml of I got some problems > > First some elements need to be re-ordered - no big deal. But: [...] > > 2) Every changelog-item is also of type "release". But do you really > > think a complete changelog should include the "filelist" for every > > release? With some packages this might extremely increase the size > > of the package.xml. Is it useful for anything? > > Nop, the changelog tag is just that, a lazy way for storing the list > of changes (only the list). In the future the great think will be that > at "pear package" time, the pear-cmd retrieves from the web the list > of changes and create a real stand alone Changelog file for being > shippied with the release. But still it makes no sence to include a filelist for every changelog- entry, right? Then I guess we should do something here ... Maybe we could make the filelist optional? This way the worst you could have is a dummy-package without any files ... like they have in debian for pulling in dependencies :-)) Not that we should use it - but I guess that might be way - to have 0 or 1 filelist-containers for each release. > > All other things seem to work fine. Will update the > > package.xml-files in CVS according to the dtd as soon as the above > > mentioned points can be cleared. > > Prior to this step, we should provide a tool for the developers to DTD > check their package.xml files. That will happen when finish the commit > of the DTD package or well, if you do have Linux and the xmllint cmd > you could start now. Of course if we all agree with the changes to the > DTD :-) About all other changes I agree with you. Well done. Would be nice if we could finish this topic and not simply leave it uncommented on the list. Stefan