Package Proposal update: PEAR_PackageGenerate

Hello, I've made a few significant changes to the package that should make many people happy: 1) There is a complex example of how to use PEAR_PackageGenerate in the docs for the class found at: http://www.chiaraquartet.net/apidoc/PEAR_PackageGenerate/PEAR_PackageGenerate.html 2) PEAR_PackageGenerate now uses the pear installer, and depends on PEAR 1.1 so that PEAR_Common is properly setup 3) new methods PEAR_PackageGenerate::addRole() and PEAR_PackageGenerate::addDependency() simplify the addition of new file extension => install role mapping, and simplify the maintenance of dependencies. 4) changelog entries are auto-generated, and intelligently replace existing changelogs for a version. Now it is possible (and advisable) to run this utility on your package every time you do an update. Docs and sources are at http://www.chiaraquartet.net/apidoc I am at full +3 with a conditional +1 from Laurent if I give an example (which is now in the docs and in a post I sent to pear.dev a few minutes ago) With 2 full +1, I will commit the package to cvs. Is everyone happy with the name? How does PEAR_PackageFile_Manager sound, is that better? Regards, Greg