Newsgroups: php.internals,php.pear.dev Path: news.php.net Xref: news.php.net php.internals:45025 php.pear.dev:52401 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91777 invoked from network); 17 Jul 2009 23:01:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jul 2009 23:01:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@beccati.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=php@beccati.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain beccati.com designates 213.92.90.60 as permitted sender) X-PHP-List-Original-Sender: php@beccati.com X-Host-Fingerprint: 213.92.90.60 ispeed-srv6.housing.tomato.it Received: from [213.92.90.60] ([213.92.90.60:49739] helo=mail.beccati.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1B/98-02180-5E2016A4 for ; Fri, 17 Jul 2009 19:01:57 -0400 Received: (qmail 58981 invoked from network); 18 Jul 2009 01:01:54 +0200 Received: from unknown (HELO ?192.168.1.201?) (matteo@beccati.com@88.149.176.119) by mail.beccati.com with SMTP; 17 Jul 2009 23:01:54 -0000 Message-ID: <4A6102D2.1000002@beccati.com> Date: Sat, 18 Jul 2009 01:01:38 +0200 User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Greg Beaver CC: Lukas Kahwe Smith , =?ISO-8859-1?Q?Johannes_Sch?= =?ISO-8859-1?Q?l=FCter?= , PHP Developers Mailing List , PEAR Dev References: <4A5FB5B9.9030402@chiaraquartet.net> <1247792699.3638.16.camel@goldfinger.johannes.nop> <4A60F535.6040307@beccati.com> <4A60FA20.7020500@chiaraquartet.net> In-Reply-To: <4A60FA20.7020500@chiaraquartet.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] better management of php-src/pear and PEAR's future in php From: php@beccati.com (Matteo Beccati) Greg Beaver ha scritto: > Matteo Beccati wrote: >> Not really: it will copy the link, not its content. At least that was my >> 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? Not sure how packaging currently works, but I'm pretty sure it is possible to extend whatever we currently have to create an svn tag and do the required changes before exporting for packaging. If needed I can help with it once the whole process is defined. Cheers -- Matteo Beccati OpenX - http://www.openx.org