Re: Package proposal: PEAR_PackageGenerate
| From: | Davey | Date: | Tue, 22 Jul 2003 18:52:28 +0000 |
| Subject: | Re: Package proposal: PEAR_PackageGenerate | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-18552@lists.php.net to get a copy of this message | ||
Looks Good!
+1
- Davey
Greg Beaver wrote:
Hi, Maintaining package releases is a headache even for smaller projects (as evidenced by the recent accidental non-inclusion of Date/Span.php in the Date package). PEAR_PackageGenerate reads in an existing package.xml file, and generates a <release></release> section, then replaces the current <release></release> tag with the new one. If the release tag is not present, the file will not be modified. Exciting features: 1) the filelist can be directly generated intelligently from a local CVS checkout, ignoring non-CVS files, as well as the old-fashioned way from a bare non-cvs directory 2) extreme control over file and directory roles, including generalities (all .gif files as role="data"), and specific exclusions (file phpdoc as role="script") 3) All of the wildcard ignore features present in phpDocumentor can be used to exclude any number of files. 4) future possibility of plugins for other filelist generation (subversion, for example). API Docs and highlighted source code are both available at: http://www.chiaraquartet.net/apidoc/ specific source code links: http://www.chiaraquartet.net/apidoc//__filesource/fsource_PEAR_PackageGenerate__PackageGenerate.php.html http://www.chiaraquartet.net/apidoc//__filesource/fsource_PEAR_PackageGenerate__PackageGenerator_File.php.html http://www.chiaraquartet.net/apidoc//__filesource/fsource_PEAR_PackageGenerate__PackageGenerator_Cvs.php.html The name is debatable, as I don't like it currently. Putting it in the PEAR Category would obviously make sense here. Note that the current version simply uses a regular expression to find the old <filelist> section, and this will have to be modified at a future date to be more intelligent, parsing the XML file, but I didn't really feel this was a pre-requisite to package proposal. If enough people feel this feature should be in the first release, I will delay release until it is implemented. Note that since I started this package late this afternoon, and it is early the next morning, I may have left out some of the documentation by accident. It is fully tested and working, however. Greg