Newsgroups: php.internals,php.pear.dev
Path: news.php.net
Xref: news.php.net php.internals:45019 php.pear.dev:52397
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: Greg Beaver <greg@chiaraquartet.net>,
 PHP Developers Mailing List <internals@lists.php.net>,
 PEAR Dev <pear-dev@lists.php.net>
Message-ID: <D2394EAD-A280-4020-B1CE-DD664C90D360@pooteeweet.org>
To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>
In-Reply-To: <1247792699.3638.16.camel@goldfinger.johannes.nop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 17 Jul 2009 21:19:28 +0200
References: <4A5FB5B9.9030402@chiaraquartet.net> <1247792699.3638.16.camel@goldfinger.johannes.nop>
Subject: Re: [PHP-DEV] better management of php-src/pear and PEAR's future in php
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 17.07.2009, at 03:04, Johannes Schl=FCter wrote:

> On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
>> I'd like to consider instead using svn:externals to pull in PEAR =20
>> 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.
>
> How does this work with tagging or releases?
> Currently the phar thing isn't tagged at all when building PHP =20
> releases,
> but I assume the svn:externals would be copied as is and might lead to
> wrong assumptions (like that a newer version was included) meaning we
> make the tagging more complex or avoiding confusion.


if you svn copy .. it will copy the externals ..

regards,
Lukas Kahwe Smith
mls@pooteeweet.org