Newsgroups: php.internals,php.pear.dev Path: news.php.net Xref: news.php.net php.internals:45011 php.pear.dev:52390 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87754 invoked from network); 17 Jul 2009 01:05:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jul 2009 01:05:09 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 83.243.58.133 as permitted sender) X-PHP-List-Original-Sender: johannes@php.net X-Host-Fingerprint: 83.243.58.133 mailout1.netbeat.de Linux 2.6 Received: from [83.243.58.133] ([83.243.58.133:53124] helo=mailout1.netbeat.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 49/81-13263-04ECF5A4 for ; Thu, 16 Jul 2009 21:05:09 -0400 Received: (qmail 12014 invoked by uid 89); 17 Jul 2009 01:29:55 -0000 Received: from unknown (HELO ?192.168.1.102?) (johannes%schlueters.de@88.217.52.223) by mailout1.netbeat.de with ESMTPA; 17 Jul 2009 01:29:55 -0000 To: Greg Beaver Cc: PHP Developers Mailing List , PEAR Dev In-Reply-To: <4A5FB5B9.9030402@chiaraquartet.net> References: <4A5FB5B9.9030402@chiaraquartet.net> Content-Type: text/plain Date: Fri, 17 Jul 2009 03:04:59 +0200 Message-ID: <1247792699.3638.16.camel@goldfinger.johannes.nop> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] better management of php-src/pear and PEAR's future in php From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=) 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 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 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. Additionally: With the current process I can be assured that the package being used is a released" package, such a linkage might catch a random dev version or bad version numbers or .... johannes