On Mon, Jul 30, 2007 at 05:14:45PM +0200, Gregory Colpart wrote: > > > All together, now that I did about 10 pear extension Debian packages or > > so, I am wondering if it was possible to create a script that would > > parse the "package.xml" file to auto generate the debian/rules file the > > correct way. An automated system would have many advantages. Some that > > come to my mind: make Debian packages very fast, reduce the possibility > > to make errors, make it possible to have updates very fast at the same > > time as the one from pear.php.net, ... > > > > Also, the package.xml has all the needed information: upstream author, > > license, and list of files and where to set them up. As it's an XML > > file, it's quite easy to parse. > > > > Of course, this doesn't mean that the resulting Debian folder shouldn't > > be check for consistency. This is the role of both the maintainer, and > > the sponsor. > > > > If anybody is interested about this idea and want to work with me doing > > it, let me know. One of the subjects that I'd like to discuss is what > > tool to use to parse the file. Maybe php itself as it can be called from > > shell? > > Parsing and displaying informations are done with: > $ pear info package.xml > > I don't think it's very useful to do more and generate > debian/control file because it could give bad habits for the > maintainer: debian/control must have ever manual checks.
Complementary information, there is such a script in dh-make-php package: /usr/share/dh-make-php/phppkginfo Regards, -- Gregory Colpart <[EMAIL PROTECTED]> GnuPG:1024D/C1027A0E Evolix - Informatique et Logiciels Libres http://www.evolix.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
