Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80750
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c_znCzyPf2K50ou_6PjA=2bZMD0tSU3VJ3hfAn6-BSOJw@mail.gmail.com>
References: <54BB7170.4060905@beccati.com>
	<CAF+90c_znCzyPf2K50ou_6PjA=2bZMD0tSU3VJ3hfAn6-BSOJw@mail.gmail.com>
Date: Sun, 18 Jan 2015 23:59:45 +0700
Message-ID: <CAEZPtU6u_qB-7G2jVEjDO4b9yMKYCy4T7t23SfEZ8hH4fnfLAw@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Matteo Beccati <php@beccati.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] PEAR and make install on master
From: pierre.php@gmail.com (Pierre Joye)

On Sun, Jan 18, 2015 at 11:44 PM, Nikita Popov <nikita.ppv@gmail.com> wrote:
> On Sun, Jan 18, 2015 at 9:40 AM, Matteo Beccati <php@beccati.com> wrote:
>
>> Hi,
>>
>> so, the removal of deprecated features has started and make install is now
>> rightfully failing because PEAR is installed by default, although it is not
>> compatible anymore:
>>
>> Installing PEAR environment:      /home/atlassian/phpNext/lib/php/
>>
>> Fatal error: Non-static method PEAR_Installer_Role::initializeConfig()
>> cannot be called statically, assuming $this from incompatible context in
>> phar:///.../pear/install-pear-nozlib.phar/PEAR/Config.php on line 599
>> make[1]: *** [install-pear-installer] Error 255
>> make: *** [install-pear] Error 2
>>
>> I've tried to look up the pear MLs, but I haven't seen any recent
>> activity... what's the plan, if any?
>>
>
> That's a good question. As far as I understand we still need PEAR because
> it also provides the PECL installer. So it would be good if the installer
> is fixed.

For pecl, we will propose to bundle pickle.phar, which basically
provides 100% bc for existing packages and allow much more, like
install from any URL/VCS based on composer, integration with composer
(composer will call pickle for any php-ext dep). Last but not least,
if one likes to drop "pecl install" support, he won't need to maintain
package.xml, duplicate versions, meta and co but only the sources,
config.* and README.

I am waiting for the discussions+RFC about how to deal with 5 and 7
extensions support. Once we have a decision we will implement what is
necessary for that in pickle.

For the ref here: https://github.com/FriendsOfPHP/pickle


Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org