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

limitations of svn:externals

From: Narayana Prasad <nprasad_at_embeddedinfotech.com>
Date: 2005-11-07 10:13:03 CET

    I was trying to move to SVN from CVS, but the lack good alias
support is preventing my group from doing so. Upon googling, i found
that svn:externals does only half of what i want. I can alias a modules
to be checkout together, but i cant get them to be committed together.
One second thoughts i realized, svn:externals is intended for a very
different purpose. It really meant for separately managed and versioned
software to have some degree of correlation. But my requirement is
within the same repository, i've common code, which is used by other
pieces of software. So every checkout, commit, tag, branch should also
reflect on the common code. But the common code must stay common and
maintain a common history.

It seems svn doesnt yet have a way to do this yet. So i have the
following proposal.
I'd like to add an "svn link" command(along the lines of ln -s). This
command create a meta-file which will be subversion link to a subversion
directory in the same repository.

    $ svn link /path/to/realdir linkdirname

Every svn command - co, ci, copy, diff, merge should then parse the
meta-file to retrieve the real repository location and perform the
operation on it. For starters i'd like at least the co, up, ci, cp and
status operations to work, since these are used most often on top-level

I'd like to know if the current developers think this makes sense and is
doable. I saw the code of svn was in C and i can C. So with some
pointers from you folks i'd like to add this functionality if it makes


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 7 10:09:39 2005

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