Newsgroups: php.internals,php.pear.dev
Path: news.php.net
Xref: news.php.net php.internals:45007 php.pear.dev:52387
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.154 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=pA9hdSEbOTP5yvUpLfA6uhsC6l12Yhdvl/OhX/DhHe2MlStc0zzeEyeHhMpv0LLf6g
         cqlPH/0EWR45KtX83X/F+ELTr2N3GOLofFSzjC45RMDX6Vp6S2yTm1Gum9GDK+O07OEb
         OKD/EtLFb3UhCAj95XoF2gvLA1FjblnCju/tQ=
MIME-Version: 1.0
In-Reply-To: <4A5FB5B9.9030402@chiaraquartet.net>
References: <4A5FB5B9.9030402@chiaraquartet.net>
Date: Fri, 17 Jul 2009 01:46:50 +0200
Message-ID: <fe05d1540907161646p629da76au7653646f74763bf0@mail.gmail.com>
To: Greg Beaver <greg@chiaraquartet.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>, PEAR Dev <pear-dev@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] better management of php-src/pear and PEAR's future in 
	php
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Fri, Jul 17, 2009 at 1:20 AM, Greg Beaver<greg@chiaraquartet.net> wrote:
> Hi,
>
> I'd like to start a discussion on php-src/pear and how we can manage it
> better for PHP 5.3, and to discuss the future of PEAR in PHP.
>
> First, take note that both internals@ and pear-dev@ are copied on this
> email.
>
> For some background, currently the pear components are dynamically added
> to a checkout by downloading from pear.php.net. =A0These components are
> install-pear-nozlib.phar and go-pear.phar (for windows). =A0In addition,
> the windows go-pear.phar is only downloaded by the build script for
> windows. =A0Although this works, it adds some obscurity to how the proces=
s
> really works.

Is it possible to have one single phar for all platforms? That would
already make the whole thing easier to manage.

> I'd like to consider instead using svn:externals to pull in PEAR stuff
> directly from a STABLE branch from somewhere in the pear/ hierarchy.
> This would allow us over at PEAR to push the installation phars into
> that branch at the same time a release is made, and would also allow
> quick fixes by a quick revert to a previous revision.

Sounds clean enough and will hopefully avoid the recent issues.

> 1) how important is the backwards compatibility of the "pear" and "pecl"
> script commands? =A0I.e. does Pyrus need to provide a way to emulate the
> interface to these scripts or can we break backwards compatibility on
> this point by having these scripts just call pyrus's frontend with
> default channels pear/pecl?

New tools, new commands. How different is it to install a package?

Too early for php6 :)

Cheers,
--=20
Pierre

http://blog.thepimp.net | http://www.libgd.org