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

[FEAT. REQ] Aggregate working copy ?

From: Dominique PERETTI <dperetti_at_lachoseinteractive.net>
Date: 2004-07-31 14:32:01 CEST

Hi all,

I've been playing a little bit with externals. This is great, but
they're only a partial answer to a problem that probably other users

I have 3 different working copies from the same repository :
- an "engine" folder (the core of a content management system we are
working on).
- a "sites" folder (web sites sharing the same engine)
- a Flash folder (mostly actionscript classes, some of them are used by
a components of the engine).

They don't reside in the same directory.

Sometimes a change in the engine in one working copy implies a change
in all working copies.
Of course, I want a single, consistent commit, for all working copies.

I first thought externals would address this problem. But this is not
exactly what I need.

I have a dream :

I want to be able to define a set of working copies. Could be in a
"aggregate.svn" file, just containing the paths of my 3 working copies.

Then, I could type :
svn status --aggregate aggregate.svn
svn commit --aggregate aggregate.svn
etc... and thus operate on all working copies at the same time.

Other approach : one could use an "aggregate folder". In this
directory, one would just put soft links to the working copies.

The benefits of such a feature would be that the user could have
locally its own layout without any required change on the repository

What do you think ?

Dominique PERETTI

SvnX, a GUI for svn on Mac OS X

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 31 14:32:59 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.