Re: Finally PEAR_PackageFileManager 1.6.0 b5 is canceled

Mark Wiesemann wrote:

My personal opinion about PEAR_PackageFileManager: It's nice to have such a package that can generate the package.xml files, but I don't see how I would benefit from it for existing packages. Updating the changelog and setting the release date needs to be done anyway -- either in the script and calling PFM after that, or by direct editing the XML file. Also for new packages it is easy to copy an existing XML file and edit it. But if the package contains a lot of files, I see a big advantage of using PFM.

I think that PFM is a great idea to use, always! It will assist in making sure the result is well formed and that you can edit things more easily than inside a gigantic XML file that contains a lot of tags you will never edit. It also makes sure you do not forget to add/remove files added in CVS. I also think that PFM will make it easier to make use of newer features of the package format, let alone migrate from version 1 to version 2. regards, Lukas