Re: clever idea for BC with package.xml 2.0?

Ian Eure wrote:

On Tuesday 19 October 2004 02:22 pm, Greg Beaver wrote:

Hi, I've just added code that would allow a .tgz package to be bundled with both a package.xml version 2.0 and version 1.0. This means the installer would first look for package2.xml, and if it finds it, ignore package.xml.

+1 Does this include a way to automatically downconvert v2.0 package.xml files to v1.0? That way, everything would automatically work with both installers.

This is not going to be built into the installer - guesswork in this area would be extremely hazardous. Fortunately, it will be built into PEAR_PackageFileManager2 (you will be able to spit out version 1.0 and version 2.0 package.xml from the same configuration), so that you can be sure it will do it right. Until I write this tool (which will be remarkably small thanks to the design of PEAR_PackageFile), it will have to be manual, but you can start with a package.xml 1.0 and use "pear convert" to convert it into a 2.0. I designed it this way because package.xml 2.0 can represent a larger set of installs than package.xml 1.0 (it encompasses every possible package.xml 1.0 and then some). Greg