You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Dominique PERETTI <dp...@lachoseinteractive.net> on 2004/07/31 12:32:01 UTC
[FEAT. REQ] Aggregate working copy ?
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
have.
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
side.
What do you think ?
Dominique PERETTI
http://www.lachoseinteractive.net/
SvnX, a GUI for svn on Mac OS X
(http://www.lachoseinteractive.net/en/community/subversion/svnx)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: [FEAT. REQ] Aggregate working copy ?
Posted by Ben Collins-Sussman <su...@collab.net>.
On Sat, 2004-07-31 at 07:32, Dominique PERETTI wrote:
>
> What do you think ?
>
You've described a feature already in our long-term plans. Namely,
.svn/entries files should be able to "link" together, even if the
working copies are from separate repositories. 'svn commit' would then
aggregate changes per-repository, and guarantee only 1 commit per
repository. In this vision, the svn:externals feature would be used
only for checkouts (initial construction of the aggregate working
copy). After that, everything would "just work" because entries files
would be directly linked.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: [FEAT. REQ] Aggregate working copy ?
Posted by Julian Foad <ju...@btopenworld.com>.
Looking through old mail, I came across this question.
Dominique PERETTI wrote:
>
> 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 have.
>
> I have 3 different working copies from the same repository :
[...]
> Of course, I want a single, consistent commit, for all working copies.
[...]
> 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.
The only reply that appeared on the "dev" list was mainly talking about the case of having working copies from different repositories. In your case I think you can just use an environment variable, like this:
AGGREGATE="engine sites Flash"
svn status $AGGREGATE
svn commit $AGGREGATE
etc.
There is also a feature just like your "--aggregate" suggestion, but called "--targets". It is available on some commands such as "svn commit", but not currently on other commands such as "svn status". I don't see any reason not to make "--targets" work on all commands that take targets.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [FEAT. REQ] Aggregate working copy ?
Posted by Ben Collins-Sussman <su...@collab.net>.
On Sat, 2004-07-31 at 07:32, Dominique PERETTI wrote:
>
> What do you think ?
>
You've described a feature already in our long-term plans. Namely,
.svn/entries files should be able to "link" together, even if the
working copies are from separate repositories. 'svn commit' would then
aggregate changes per-repository, and guarantee only 1 commit per
repository. In this vision, the svn:externals feature would be used
only for checkouts (initial construction of the aggregate working
copy). After that, everything would "just work" because entries files
would be directly linked.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [FEAT. REQ] Aggregate working copy ?
Posted by Julian Foad <ju...@btopenworld.com>.
Looking through old mail, I came across this question.
Dominique PERETTI wrote:
>
> 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 have.
>
> I have 3 different working copies from the same repository :
[...]
> Of course, I want a single, consistent commit, for all working copies.
[...]
> 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.
The only reply that appeared on the "dev" list was mainly talking about the case of having working copies from different repositories. In your case I think you can just use an environment variable, like this:
AGGREGATE="engine sites Flash"
svn status $AGGREGATE
svn commit $AGGREGATE
etc.
There is also a feature just like your "--aggregate" suggestion, but called "--targets". It is available on some commands such as "svn commit", but not currently on other commands such as "svn status". I don't see any reason not to make "--targets" work on all commands that take targets.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org