Description: ------------ PHPDoc has: <file role="script" baseinstalldir="/" md5sum="846753fcbcce322a1a5c2039f7742827" name="phpdoc"> <replace from="/usr/local/bin" to="PHP_BINDIR" type="php-const"/> <replace from="@data_dir@" to="data_dir" type="pear-config"/> <replace from="@doc_dir@" to="doc_dir" type="pear-config"/> <replace from="@php_dir@" to="php_dir" type="pear-config"/> </file> but this does not appear in the output RPM spec file (should be /usr/bin/phpdoc). Maybe role=script isn't being handled properly somehow. Superficially it looks OK but there's obviously an issue.

This is true for the (not deprecated) PHPDocumentor package too. After analysis, it seems that the basic issue is that the current template.spec uses %{peardir}/* in place of the @files@ macro, which means that files other than role=php are basically ignored (even though PCP internally processes them and puts them into the @files@ macro). However, using @files@ results in a vast list of files for many packages, which is not really necessary. A compromise would be to introduce additional macros for roles other than PHP files (similar to how docs are currently handled) and use those in addition to %{peardir}/*. I am working on this.

Packaging.php v1.22 in CVS now adds several @[role]_files_statement@ macros, which partially solves this bug. I had hoped it would solve the entire bug, but this then threw up the fact that PHPDocumentor uses "install as", which is not currently handled - see bug #10327.

Fixed in CVS thanks to the solution to bug #10327.