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

Foreign repository

From: Lele Gaifax <lele_at_nautilus.homeip.net>
Date: 2004-05-15 01:53:34 CEST

Hi all,

I'd like to track foreign svn repos in mine. This is a lot simpler
case that two way sync, as all I need is the capability, from time to
time, to merge remote changes in.

I found that `svn copy` does not cope with this, and tells me that
since the source is a foreign repository, it will leave the copy as a
detached wc, that is, something very similar to a plain checkout.

Looking at the source, the problem seems related to svn_wc_add() not
being able to do the right thing when its copyfrom_url argument is
NULL. The comment says:

     ### Someday, we would just call svn_wc_add(), as above,
     but with no copyfrom args. I.e. in the
     directory-foreign-UUID case, we still want everything
     scheduled for addition, URLs rewritten, and wcprop cache
     deleted, but WITHOUT any copied flags or copyfrom urls.
     Unfortunately, svn_wc_add() is such a mess that it chokes
     at the moment when we pass a NULL copyfromurl.

So I tried the export approach followed by an add. This worked, of
course, and I was able to effectively track the foreign repos by
merging from it. Unfortunately, the merge operation fails when a file
is added, reporting an unsupported feature. The source reveals that
it's probably a protection against the same svn_wc_add() limit.

Any hint on how should that function behave?

Thanx a lot,
ciao, lele.

nickname: Lele Gaifax	| Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas	| comincerò ad aver paura di chi mi copia.
email: lele@seldati.it	|		-- Fortunato Depero, 1929.
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 15 01:53:56 2004

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.