Re: package.xml 2.0 dilemma
| From: | Greg Beaver | Date: | Thu, 09 Jun 2005 02:13:59 +0000 |
| Subject: | Re: package.xml 2.0 dilemma | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-38046@lists.php.net to get a copy of this message | ||
Alan Knowles wrote:
I would say if you're always happy with the auto-convert, perhaps an option to pear package would fix this? $ pear package --convert GregFor a simple package like the svn extension, I would recommend simply maintaining the package.xml 1.0 and use "pear convert" to spit out an equivalent package.xml 2.0.is there any reason why "pear package" can not run "pear convert" internally to generate a package2.xml which is only stored in the tarball? None other than the severe risk of magic involved. Several elements not present in package.xml 1.0 are added (guessed) by the conversion process, particularly a php dependency (it guesses 4.0.0 or higher if nothing is specified).