Newsgroups: php.internals,php.pear.dev
Path: news.php.net
Xref: news.php.net php.internals:45030 php.pear.dev:52406
Return-Path: <mweierophinney@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 22005 invoked from network); 18 Jul 2009 22:09:09 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 18 Jul 2009 22:09:09 -0000
Authentication-Results: pb1.pair.com header.from=mweierophinney@gmail.com; sender-id=pass; domainkeys=bad
Authentication-Results: pb1.pair.com smtp.mail=mweierophinney@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.228 as permitted sender)
DomainKey-Status: bad
X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01
X-PHP-List-Original-Sender: mweierophinney@gmail.com
X-Host-Fingerprint: 209.85.219.228 mail-ew0-f228.google.com  
Received: from [209.85.219.228] ([209.85.219.228:45025] helo=mail-ew0-f228.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 53/AF-02180-408426A4 for <pear-dev@lists.php.net>; Sat, 18 Jul 2009 18:09:09 -0400
Received: by ewy28 with SMTP id 28so1631672ewy.23
        for <multiple recipients>; Sat, 18 Jul 2009 15:09:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        bh=idB2WR76fSGLju7XkFezh4UZMORW4tm+JQIk+9ElNdY=;
        b=dlDtEj5BCVMZIf1NYYzyp1xMEMMjK3VXPkpqMAv0n6biDQBk2JLv/W1W523S0MooO+
         eG9jGto4ysxqyBPV34cutFz2xRi+x0csWQhO9294pPU/QSwQebAdHyxmRK90ak7wZkxW
         Hn2lNRqKqgdAEQYdti8Pjr73wJ+PmGgHHELII=
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=WC9FCxuQfb5ae4nKXDeVD4lkyu7MJq6zMq4Xsy+9sJA/G5N4nRKAzSkVTIeoXGOkQm
         kPQprgrs03dH9IHpBKKFqvHurzkqa6WhM3BduH57wmGB9pug4Y+yCTevb3jLiiifvyKS
         ibcmxvJz33emZ4r37FpLclF73TIHEkCuI+F/c=
MIME-Version: 1.0
Received: by 10.216.3.206 with SMTP id 56mr708121weh.99.1247954945304; Sat, 18 
	Jul 2009 15:09:05 -0700 (PDT)
In-Reply-To: <4A60FA20.7020500@chiaraquartet.net>
References: <4A5FB5B9.9030402@chiaraquartet.net>
	 <1247792699.3638.16.camel@goldfinger.johannes.nop>
	 <D2394EAD-A280-4020-B1CE-DD664C90D360@pooteeweet.org>
	 <4A60F535.6040307@beccati.com> <4A60FA20.7020500@chiaraquartet.net>
Date: Sat, 18 Jul 2009 18:09:05 -0400
Message-ID: <afc23ac20907181509h698fb8a2p71445bb0d6005cbd@mail.gmail.com>
To: Greg Beaver <greg@chiaraquartet.net>
Cc: Matteo Beccati <php@beccati.com>, Lukas Kahwe Smith <mls@pooteeweet.org>, 
	=?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>, 
	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: [PEAR-DEV] Re: [PHP-DEV] better management of php-src/pear and 
	PEAR's future in php
From: mweierophinney@gmail.com ("Matthew Weier O'Phinney")

On Fri, Jul 17, 2009 at 6:24 PM, Greg Beaver<greg@chiaraquartet.net> wrote:
> Matteo Beccati wrote:
> > Lukas Kahwe Smith wrote:
> > > 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 =
stuff
> > > > > directly from a STABLE branch from somewhere in the pear/ hierarc=
hy.
> > > > > This would allow us over at PEAR to push the installation phars i=
nto
> > > > > that branch at the same time a release is made, and would also al=
low
> > > > > 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 rele=
ases,
> > > > 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 ..
> >
> > Not really: it will copy the link, not its content. At least that was m=
y
> > experience when I managing releases for an internal project using
> > externals. What I usually did was to change the externals property to
> > point to a specific revision, e.g.
> >
> > Property svn:externals set to
> > foo -r33165 https://svn.example.com/bar
> >
> > Depending on the process it can either be done in the branch before
> > tagging or on the tag itself.
> >
> > As a result exporting a tag will consistently retrieve the same version
> > of the external resource even years after packaging.
>
> This sounds easy to forget - is it possible to script this?

Yes -- we do it in ZF as we pull in Dojo via svn:externals.

We use "svn propget" to find where the svn:externals point, and then use
"svn info" on that externals URL to determine what the current revision
is. When we build the tag, we then create a new svn:externals definition
for the new tag that pins to that specific revision.

I'll find the relevant code from our build scripts and paste it in here
if you need specifics.

--=20
Matthew Weier O'Phinney
mweierophinney@gmail.com
http://weierophinney.net/matthew/