Re: deprecating package.xml 1.0
| From: | Greg Beaver | Date: | Tue, 22 Feb 2005 22:49:51 +0000 |
| Subject: | Re: deprecating package.xml 1.0 | ||
| References: | 1 2 3 4 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-2536@lists.php.net to get a copy of this message | ||
Lukas Smith wrote:
well looks like a short guide is what we need :-) does it work in the other direction as well or is the package.xml 1.0 automatically generated when packaging with a package.xml 2.0 on pear 1.4+?Well, this is a lot more complicated. PEAR_Common::infoFrom*() can be used to sort of convert a package.xml 2.0 into package.xml 1.0 (that's how pearweb continues to work with PEAR 1.4.0a1), but there is nothing automatic here. The only requirement for validation is that every file in package.xml must be in the package2.xml, and not vice-versa. This is because package.xml version 2 allows files to be distributed in the archive that are not ever installed, which will be useful for things like phpDocumentor, as we can distribute a single tarball for both sourceforge and for PEAR install. Greg