I'm doing some development of what hopefully will be an addition to PEAR and I want to see the fruits of my labor (the boring hours of adding somewhat meticulous PHPDoc comments). Wondering if we can see an ebuild for phpDocumentor. I'll download it and see if I can whip one up.
http://pear.php.net/package/PhpDocumentor Realized that this package is already part of PEAR. Should make life easier for us.
Yeah using your standard PEAR-* ebuilds for XML_Beautifier and PhpDocumentor worked like a champ. PEAR-PhpDocumentor should DEPEND on PEAR-XML_Beautifier. I've only tested install, haven't tested use. I have to run to bed now but I'll try and get more testing and post ebuilds if still needed tomorrow.
I'm getting an error trying to install PhpDocumentor, it errors out on the -R ${D}. If I take that clause out I can install it just fine. Otherwise I get this error: # pear install --nodeps -R /var/tmp/portage/PEAR-PhpDocumentor-1.2.3/image/ package.xml Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 2828 bytes) in /usr/lib/php/PEAR/Installer.php on line 259 Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 0 bytes) in Unknown on line 0 I didn't get these errors when testing my ebuilds last night at home.
FWIW: $ pear -V PEAR Version: 1.3.1 PHP Version: 4.3.6 Zend Engine Version: 1.3.0 Running on: Linux orthanc 2.6.6 #1 Tue May 11 09:43:21 CDT 2004 i686
Upping the memory limit to 12M in php.ini worked. Not sure how we'd like to handle this. Should I put a pkg_setup() message in to do that if it fails? Or do we want to up the limit on the pear command line in the php-pear.eclass?
dev-php/PEAR-XML_Beautifier-1.1 committed.
dev-php/PEAR-PhpDocumentor-1.2.3 added. I'll leave the memory issue up for discussion, since this package installed fine at home, just my work machine (which is sort of flaky to begin with) had the memory issues.
