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

FREQ: Recursive WCs

From: Aaron Digulla <digulla_at_hepe.com>
Date: 2005-01-12 21:00:55 CET


With some versions of CVS, you could do this "trick":

cvs co server.../a
cd a
cvs co server.../b

An update in a would update b as well. A commit in a would commit b, too.

Is there a way to do this with svn?


I have a project with contains the main trunk, contrib code and test code.

The main code has a MPL-style license, while contrib code has all kinds
of licenses (GPL, BSD, MPL, public domain). Test code is similar.

Now, with CVS, I would checkout the contrib and test trees inside the
main WC and my makefiles would discover these files and build the files
in there as well. Also, the lawyers would be happy because the LICENSE
file in the contrib dir would read "everything below here has various
licenses. See the LICENSE file in each directory".

And I would be able to update everything at once with just one command.

If this is not possible with Subversion, I'd like to request this feature:

During update:
        - List files in the current directory
        - If item is not in .svn/entries
                AND item/.svn is a valid subversion directory
                THEN start a new sub-instance of Svn and update the
                        files in ./item/

During status:
        - Run status in ./item/

During commit:
        - Print a warning that the files in ./item are ignored
        - Continue with the next item


Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 12 21:01:31 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.