Re: Overhauling lang/pear

[Jonathan Perkin <jperkin%pkgsrc.org@localhost>]

* On 2025-06-11 at 13:29 BST, Benny Siegert wrote:

> I am confused about this bit in the patch:
>
> +DISTNAME= pearweb_phars-1.10.24
> +PKGREVISION= 3
> +PKGNAME= ${PHP_PKG_PREFIX}-pear-1.10.16
>
> Why does 1.10.24 include pear 1.10.16? Is that just an upstream oddity?

Right, I tried to explain that in the comment at the top of the Makefile, 
but it may need to be improved.

The PEAR source code does not include any way to actually install it.  

Until now we've used a separate installer called go-pear which was saved 
in FILESDIR and modified directly, so that it wasn't clear what were 
pkgsrc changes compared to upstream, and also it no longer worked.

I've now switched to using a different installer as recommended by 
upstream called pearweb_phars which is basically an installer plus all 
of the PEAR source code and dependencies all bundled together in an 
archive file, but that has a completely different version number to the 
PEAR version that it bundles.

I don't know why upstream make it as confusing as possible.  I've tried 
to simplify and standardise things as much as possible.

> The page at https://pear.php.net/manual/en/installation.getting.php
> says something like
>
> > When using PHP, the PEAR Package Manager is already installed unless one has used the ./configure option --without-pear.
>
> So should we have a separate pear package at all? Should we build it
> from the PHP tarball?

That would make sense to me, but I assume there are good reasons for 
doing it this way.

--
Jonathan Perkin                    pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com