Re: granting temporary permission for releasing packages that need

Davey wrote:

Greg Beaver wrote: The only problems I can forsee with such a system are these: 1) What if there things that are incomplete? I assume you mean to run it on the current CVS version? 2) The last thing most developers probably write, is package.xml, therefore any cvs version is most likely out of date.

This is not actually possible unless the developer has not committed changes to the code - I'm not talking about the contents of the package.xml, I'm talking about the contents of php files in CVS itself. PEAR_PackageFileManager ignores the pre-existing <filelist> tag, and generates a new one based on the files that are in a CVS checkout, or based on the files in a subdirectory (if the file generator is checked). That's why it's so useful, it won't allow you to accidentally forget a file in a release, you have to explicitly ignore one through a full path or wildcard expression if you don't want it listed. <advertisement role="shameless">it's really pretty great :)</advertisement> Greg