Newsgroups: php.internals,php.pear.dev
Path: news.php.net
Xref: news.php.net php.internals:45010 php.pear.dev:52389
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.159 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=JCIEHMm2f70vMr8XdcomQomuI5fkOIW5JKq/pyvlLM4oqymxnYsCTLIUKElh83d9yQ
         A1E+U/KX+OJBEnV74AQ98yNNp8QoW6lSskvUTIYfWiHS2bPiXvY6unHiBmemelECxuxy
         4cGZlnHOHXbP/5qe/f3rhMDfeQ7HhvneCK9+E=
MIME-Version: 1.0
In-Reply-To: <4A5FC46C.8020302@chiaraquartet.net>
References: <4A5FB5B9.9030402@chiaraquartet.net>
	 <fe05d1540907161646p629da76au7653646f74763bf0@mail.gmail.com>
	 <4A5FC46C.8020302@chiaraquartet.net>
Date: Fri, 17 Jul 2009 02:36:18 +0200
Message-ID: <fe05d1540907161736i25b1002fh2bcafedd1aebf0e5@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)

On Fri, Jul 17, 2009 at 2:23 AM, Greg Beaver<greg@chiaraquartet.net> wrote:

>> Is it possible to have one single phar for all platforms? That would
>> already make the whole thing easier to manage.
>>
> This would be more challenging to do, but may be possible. =A0The biggest
> problem is that go-pear is interactive, and install-pear is not.
>
> One thing that is good to note is that both go-pear/install-pear may be
> obsoleted by Pyrus since it doesn't need to be installed to work. =A0The
> only thing that we'd need to distribute would be scripts to invoke
> Pyrus. =A0My question is mainly whether to make stub "pear" and "pecl"
> scripts that will invoke Pyrus, and if these should pretend to be PEAR
> (support some of the more obscure things PEAR supports).

Even better :)

>> New tools, new commands. How different is it to install a package?
> Basic stuff is all the same, install/upgrade/uninstall work as PEAR
> does, identical syntax and all. =A0Some of the more obscure stuff has bee=
n
> removed, such as --soft, --register-only and --ignore-errors.
> Configuration has changed a bit, and the config-set command has been
> replaced with just "set" =A0The "info" command performs the duty of both
> info and remote-info, and remote-list has replaced list-all. =A0In
> addition, the --installroot option as implemented by PEAR (which was
> always strange) is gone, --packagingroot is the option for those doing
> RPM building.
>
> Pyrus, however, is alpha, which is why I'm asking what is really
> important, we can still change it if anything is really crucial.

I would go with the new syntax, there is no need to keep BC here.

Cheers,
--=20
Pierre

http://blog.thepimp.net | http://www.libgd.org