On Sun, Jan 25, 2015 at 3:18 PM, Lester Caine <les...@lsces.co.uk> wrote:

> On 25/01/15 13:52, Matteo Beccati wrote:
> > Not yet. For now, use --without-pear.
>
> Just for the record ... There have been various comments about PEAR's
> future. There is a substantial base of code using it. However the
> versions downloaded direct may not actually be usable currently so some
> plan to make that code base usable again probably needs to be on the
> PHP7 todo list?
>
> I will cross check the PEAR modules I am currently using when I get that
> far since they have already been made e_strict clean.
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
I've added a PR for pear-core(https://github.com/pear/pear-core/pull/33),
with those fixes I was able to build a install-pear-nozlib.phar which when
copied to php-src/pear/ made make install without error (and I was able to
install pear/pecl packages so it seems to be working fine)
As I mentioned in the PR, I think it is likely that we will be other
upcoming BC breaks requiring changes in PEAR, so instead of requiring a
PEAR release and rebuilding http://pear.php.net/install-pear-nozlib.phar I
would suggest having a php7 compatible install-pear-nozlib.phar committed
to php-src for now (until we have release freeze with php7).
What do you think?

-- 
Ferenc Kovács
@Tyr43l - http://tyrael.hu

Reply via email to