Thanks for both your answers Matthew.
On 11 Mar 2009, at 15:09, Matthew Weier O'Phinney wrote:
-- Carlton Gibson <carlton.gib...@noumenal.co.uk> wrote
(on Wednesday, 11 March 2009, 01:29 PM +0000):
On 11 Mar 2009, at 13:11, Jan Wagner-Rosenkranz wrote:
Carlton Gibson schrieb:
I'm looking to checkout the ZendX library as a svn:external. I was
hoping to just target a release tag but there aren't any defined in
/extras/tags.
I use:
http://framework.zend.com/svn/framework/extras/branches/release-1.7/library/ZendX
Jan,
Thanks for your suggestion. My only concern is that this is still
subject to changes. That's why I'm after a tag.
Two things with regard to this. First, changes merged to a release
branch are primarily bugfixes, and should always be backwards
compatible.
Okay, since this is the case I'll probably go with Jan's approach.
Second, if you want to ensure that the revision does not change... pin
to a specific revision. svn:externals supports that natively. As an
example, you can use something like the following:
externals/extras r14722
http://framework.zend.com/svn/framework/extras/branches/release-1.7/library/ZendX
I gave a made-up revision number there, but that's the basic idea --
you
can specify a revision between the local path and the externals path.
This was what I had in mind (but the syntax is helpful).
Thanks again.
--
Matthew Weier O'Phinney
Software Architect | matt...@zend.com
Zend Framework | http://framework.zend.com/
