pear convert

Hi, As we get closer to PEAR 1.4.0 being a reality, I have a few updates. I have not completed work on supporting the internals of package.xml version 2.0, including installation, packaging, and uninstallation as well as all that bundles crap argued about. I have completed work on package.xml 1.0 features including: - full dependency resolution pre-download (works for the most complex tests cases I could find without an outright regression test - this is next) - installation from any source that 1.3.x can install from - uninstallation - packaging with full validation, including version number/state validation (you can't release version 0.1.0 stable, or 1.0.0 alpha any longer) Most exciting, there is a command that can help users migrate to the package.xml 2.0 format to take advantage of the advanced features. $ pear convert Run this from the directory containing package.xml, and it will spit out a package2.xml in version 2.0 format. (pear help convert for options) Note that because of the way PEAR needs filelists (flattened into a single set of file tags), when it regurgitates a recursive filelist, baseinstalldir will be repeated for every file. To fix this, you have to manually modify the file after it is created. PEAR_PackageFileManager will provide a more elegant way to create a package.xml, this is for developers only, to get familiar with the new format before it is fully documented, or to automatically convert an old package into a new one prior to manual tweaking. This is also a good chance to review what is being changed. Some of the basic concepts behind 2.0 are very different from 1.0, both to allow greater flexibility as well as better organization. It should be noted that tag order is important in 2.0, the validation mechanism will let you know if things are in the wrong order. Validating is much, much more complex if things are out of order, at least until PEAR 2 and we can just plug in a schema for validation using libxml. Greg