Re: Package proposal: PEAR_PackageGenerate

Laurent Laville wrote:

Hello Greg

Maintaining package releases is a headache even for smaller projects

i think that eveybody is agree with you, even if trying to create without support a first package is a good experience !

API Docs and highlighted source code are both available at: http://www.chiaraquartet.net/apidoc/

Did you have some examples of uses to give us ? myself i'll greatly appreciated it and if what i think is true your package is what i've dreamed ! And you made it a reality : thanks Greg for all PEAR users If you can give us theses few examples, i'll give to you a big +1!

Hi Laurent, http://www.chiaraquartet.net/apidoc/PEAR_PackageGenerate/PEAR_PackageGenerate.html has a complex example (it weighs in at a whopping 15 lines of code) that includes ignoring a file and a directory with all subdirectories, installing a specific file into another baseinstalldir, redefining the role for all files in a directory and its subdirectories, and redefining the role for 2 specific files, as well as adding a new generalization of file extension to role. Here is the simplest example of how to use the package: <?php require_once('PEAR/PackageGenerate.php'); $packagexml = new PEAR_PackageGenerate( array('baseinstalldir' => 'MyPackage',

        'version' => '1.0',
        'packagedirectory' => '/path/to/mypackage/',
        'state' => 'stable',
        'filelistgenerator' => 'cvs', // generate from cvs,
        'notes' => 'release notes',
        'changelognotes' => 'changelog notes'
       ));

$packagexml->writePackageFile(); ?> This example will read in the package.xml file, replace the filelist with a listing of all files found in the cvs checked-out directory /path/to/mypackage and its subdirectories, generate a changelog entry with the changelog notes, or overwrite an existing changelog for the same version number. Regards, Greg