ports/86098: [PATCH] devel/pear-PEAR/Makefile.common: allow use by foreign packages

Roman Neuhauser neuhauser at sigpipe.cz
Wed Sep 14 22:44:15 UTC 2005


# antonio at php.net / 2005-09-14 19:15:46 -0300:
> Roman Neuhauser wrote:
> ># antonio at php.net / 2005-09-14 18:14:16 -0300:
> >
> >>	SimpleTest isn't a PEAR package and I don't think it's a good idea 
> >>	have "alien" packages using Makefile.common.
> >
> >    Why?
> 
> 	Because it's not part of the PEAR PHP Framework.

    Is there a *technical* reason?

> The author should follow the formal proposal process 
> (http://pear.php.net/manual/en/newmaint.proposal.php) to have his 
> package added to the framework.

    No, there's just no reason. That's like saying that people shouldn't
    create packages for use with pkg_add unless the ports are in FreeBSD
    proper. pear.php.net supports alien packages, see the bottom of
    http://pear.php.net/packages.php

> 	Try to have a look at devel/beautifyphp.
 
    Anything particular to look for?

> >> Besides that, this port should not install files inside
> >> /usr/local/share/pear ...
> >
> >
> >    Ok, where does pear(1) normally put e. g. Horde when you install it
> >    using their package.xml files?
> 
> 	The Horde port installs its required PEAR packages via RUN_DEPENDS. 

    Ignore ports for a while. Go to http://pear.php.net/channels/,
    follow the link to http://pear.horde.org/, and install Horde_VFS
    using the procedure described there, which is:

    pear install http://pear.horde.org/Horde_VFS-0.0.1.tgz

    Where will it be installed (on FreeBSD, with PHP / pear(1) from ports)?

> When you install that packages using pear(1) directly it would place 
> them inside the php_dir (defaults to /usr/lib/php).

    Well, it's /usr/local/lib/php/pear on this box (php4-pear-4.3.11_1),
    which means ports-installed pear puts packages in a directory that's
    not in include_path, and that smells like a bug, but...

-- 
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



More information about the freebsd-ports-bugs mailing list