devel/pear or lang/php5 leaves include_path unusable

[Roman Neuhauser]

I'm writing a port for a program written in PHP 5.  It depends (BUILD_
and RUN_) on ${PEARDIR}/Console/Getopt.php:devel/pear, unfortunately
devel/pear simply informs the user that they need to configure php.ini
(see devel/pear/files/pkg-message.in), and my port needlessly fails
during the build target.

What is the reason devel/pear requires manual intervention?  Python
ports don't require the user messing with sitepkgdir to work, the base
ports set everything correctly upfront.

I could check whether "include 'Console/Getopt.php';" succeeds in
pre-build, but that won't save me from IGNORE, and I want the package.
The goal is to be able to pkg_add -r myport on a freshly installed
computer, and have a fully functional installation of myport
automatically.

-- 
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man.  You don't KNOW.
Cause you weren't THERE.             http://bash.org/?255991