progress update on PEAR 1.4.0

Hi, I've slogged through regression testing of most of the PEAR_PackageFile_v* classes, which means that although downloading has been rigorously tested, and installation partially tested, the road to packaging is finally starting to look somewhat tested too :). On that idea, I just added the ability to package up a new and an old package.xml in the same tarball. The command syntax is: $ pear package package.xml package2.xml where one of these (package.xml) is in version 1.0 format, and the other (package2.xml) is in version 2.0 format. Command-line order is insignificant. The package2.xml will be used to retrieve the filelist, so it's assumed that you will be a good developer and define the same or a very similar filelist for the package.xml. I might make this more restrictive, but at this point, the basic idea is that if you are doing this, you are using some kind of package.xml-generation program like the vaporware PEAR_PackageFile2, so that there are no errors possible. WARNING: THE NEXT STUFF MAY MAKE IT DIFFICULT TO DOWNGRADE TO PEAR 1.3.3 ON WINDOWS In any case, if you want to play around with what this creates, try checking out cvs and running: $ pear upgrade package-PEAR.xml $ pear package package-PEAR.xml package2.xml This will generate PEAR-1.4.0a1.tgz, containing both package.xml and package2.xml, and will install successfully using the package.xml for older PEAR versions, and package2.xml for the new one. You can also see a real, live package.xml in version 2.0 format there. Greg