Re: sources for PEAR_PackageFileManager

Hi Laurent, I've release 0.2 to address the issues you raised. Now, it is possible to generate a new package.xml from scratch, and provides is automatically added for all role="php" files. I decided not to bloat the source with functions for summary/description, these should be passed in the options array, since they are static. Greg Laurent Laville wrote:

Greg, I've tried PEAR_PackageFileManager 0.1 alpha, and after bad attempts, i've some requests : Is it possible to have in minds to create a full package.xml starting from no scratch. If i've well understood, you've to begin from an existing xml file or it won't work . But as i newbie i was (in package builder) few hours ago, my major problems comes from "What should i do , and how ?" And probably i'm not alone in PEAR community to ask these questions ! So i've begun to read and parse PEAR/Common.php and PEAR/Packager.php files to learn more. Finaly i've wrote a bit of script like the one joined to mail (see attachment). Also, is it possible to include as new features : - a function to analyse source (see function analyzeSourceCode) - a function to add provides class/func ... - a function to add maintainers - a function to add summary, description and all others i've probably forgotten. I know that your package is a draft : a good draft i would tell . Keep on to make us dream :o) Regards Laurent