[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Revisions of external folders

From: Alex R. Mosteo <alejandro_at_mosteo.com>
Date: 2005-01-14 17:57:54 CET

Reinhard Brandstädter wrote:


> If this is the behavior of subversion in the current implementation this
> means:
> Definitely "freezing" a repository (meaning checked out tags are always
> identical even if the referenced external repositories change) with external
> definitions by tagging it only works if external properties are set with the
> -r option or also freezed tags of the external repositories are used.


> A use case:
> We have a repository for a project; If we do a release or beta build the state
> of the repository trunk is tagged. Now we use externals pointing to another
> repository (libraries). If I want to do a rebuild of the tagged project later
> on I can't ensure that the build based on the checked out tag will be
> absolute the same as tat the time the tag was made since the lib-repository
> might have changed. This is the case unless you used the -r option on the
> external property or point to a (read-only) tag.

That's exactly what I want. I store versions of my project and want to
be able to check these out and compile out-of-the-box, pulling the
needed libraries at the revision they were when the tag copy was made.

But as I said before, when doing a tag copy I see that the svn:externals
property is missing in the copy. So there's a extra step to do to
migrate the properties. Can someone please confirm this?

I've given a second read to the svn book and I see nothing helpful in
the svn:externals section. The point on vendor branches seems to address
this problem, but I don't want to have several copies of my own
libraries in several repositories :(


A. Mosteo.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 14 18:25:28 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.