Re: Using Pear to install PECL_Gen

Gordon Heydon wrote:

Hi, Thanks for this, I am in the process of installing it. Thanks Gordon On Wed, 2005-06-22 at 09:07 +0200, Hartmut Holzgraefe wrote:

Gordon Heydon wrote:

I was triing to install PECL_Gen via pear and it is trying to build c code, of which there is none,

...

Can someone help as I would really like to user PECL_Gen to create an extension, and pear is a nice easy way to install it.

the PECL site currently checks whether a package contains C code on upload. I tried to trick it by adding a dummy void.c file but as you can see this didn't work, and i can't remove the file from the package either as this new package again isn't accepted by the upload script :(

Couldn't this simply be removed from the pecl.php.net check for PECL_Gen? Writing an exception to the rule would be exceedingly easy and would make a lot of sense, i.e. if ($package != 'PECL_Gen') {

    // check for src files

}

I'm currently aiming at moving back to PEAR (also because i am working on splitting it into a general CodeGen and a PECL specific CodeGen_PECL package, there will also be a CodeGen_MysqlUDF for MySQL User Defined Functions ...). But so far the only way to install is to fetch the current source from CVS and doing a "pear install package.xml" from within the pecl/PECL_Gen directory. PS: maybe a "pear install-from-cvs" command would be a GOOD THING(TM)?

no it would be a horrendous thing. $ cvs co module $ pear install package.xml is far more reliable. There is no standard way to grab files from cvs without some extensive code in PHP or an extension - neither of which exists yet. I don't plan to write it either, nor would I ever volunteer to maintain such a beast :). Harmut, I would also love to offer any assistance needed to make PECL_Gen work with package.xml 2.0 as well. You would benefit mightily from using PEAR_PackageFileManager for the actual package.xml generation, as it can now generate both 1.0 and 2.0 versions. Regards, Greg