Lukas Kahwe Smith wrote: > > On 17.07.2009, at 03:04, Johannes Schlüter 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/ 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. > > > if you svn copy .. it will copy the externals ..
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. Cheers -- Matteo Beccati OpenX - http://www.openx.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
