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

Re: Newbie ?: sharing code between projects

From: Jonathan Smith <jonsmith_at_members.limitless.org>
Date: 2003-05-30 00:49:15 CEST

> Ahhh, I see; if you checkout the meta-project at -r100, you want the
> external modules to *also* be at r100.

That's my problem with externals :-( Its a shame that the external can't
track the revision of the other repository.

Does svn even guarantee the atomicity across an external? the transaction
of the main repository and the transaction of the external have to both be
guaranteed success before either should be comitted. If that is the case,
then it shouldn't be much to get the revision of the external. The
question becomes how its stored. I would think you would store on the
transaction the revision of the external and use the most recent
transaction to alter an external. Finally, you would have to manually
change the version of the external to get a more recent version. I can
see the merrit in being able to track the HEAD, the latest of a given
branch, or specific versions.

I haven't decided what I'm going to do on this. We'll likely just bite
the bullet and put everything into two repositories -- one of code that
can be distributed and one of code that can't. I believe we can
selectively svn dump from a repository so we only ship the desired parts
out on CD.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 30 00:47:39 2003

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

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