Subversion problems

Thiago Macieira thiago.macieira at kdemail.net
Thu Feb 17 10:42:57 GMT 2005


Stephan Kulow wrote:
>1. kde-common/admin - the support for svn:externals is in no way
> comparable to what we did with CVS's modules: a) we can't have no way
> to use use relative paths there, so we need to add a external property
> to all branches and tags using e.g. a full https URL - most likely
> anonymous, that even ssh users would have to check out. b) I didn't
> find a way to do add such a property without checking out all
> branches/tags and honestly: I'm not going to do that.

I think we can do that with -N  (no-recurse) checkouts along with svn ls. 
I have been experimenting with that and it seems to work. So no need to 
checkout the entire branches/ or tags/ tree.

I had been expecting the need for an absolute URL with svn:externals and 
hence the need for an anonymous access to kde-common/admin. I don't think 
there's a way out, unless you ask people to ln -s kde-common/admin to 
every module.

Hmm... hold on for a minute. I've just got an idea: symlinks

$ ln -s ../kde-common/admin admin
$ svn add admin
$ svn ci admin -m "Adding admin"
Adding         admin
Transmitting file data .
Committed revision 31.
$ cd ..
$ rm -rf kdelibs/
 svn up kdelibs
A  kdelibs
A  kdelibs/admin
Updated to revision 31.
$ ls -l kdelibs/
total 0
lrwxrwxrwx  1 thiago thiago 19 2005-02-17 08:38 admin 
-> ../kde-common/admin

$ svn diff -r 30:31
Index: kdelibs/admin
===================================================================
--- kdelibs/admin       (revision 0)
+++ kdelibs/admin       (revision 31)
@@ -0,0 +1 @@
+link ../kde-common/admin
\ No newline at end of file

Property changes on: kdelibs/admin
___________________________________________________________________
Name: svn:special
   + *

Does this solve our problems?

>Now I would like to have some input on the problems we face. Would you
> prefer to not loose the date<->revision mapping or doesn't it matter?

I think losing the full functionality forever is not interesting. If it's 
just for the imported repository, I'd say it's ok. And it is preferrable 
to have several shorter downtimes, IMHO.

Now, if we take the step-by-step solution, we have to take care about 
branches being changed in both Subversion and CVS. It isn't a good idea 
to rename the branches in Subversion, then cvs2svn more data into them.

(Look at our current /branches/KDE* to see what I mean)

-- 
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

2. Tó cennan his weorc gearu, ymbe se circolwyrde, wearð se cægbord and se 
leohtspeccabord, and þa mýs cómon lator. On þone dæg, he hine reste.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050217/75138a1a/attachment.sig>


More information about the kde-core-devel mailing list