You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Holger Stratmann <ti...@finch.de> on 2005/06/20 19:40:21 UTC
no atomic commit due to layout-problems?! mixed wc...??!
Hi everybody,
I had a really hard time finding a good subject line and I'm afraid I
failed...
Anyway, here's what I mean:
From the "old CVS days", we have a repository which has "modules" at
the top of the structure.
|- module1
| |- src/com/.../...
| '- web/html/.../...
|- module2
| |- src/com/.../...
| '- web/html/.../...
|- framework
| '- src/com/.../...
'- web/.../...
For a decent IDE-/project-setup, this structure is reversed during checkout:
|- com
| '-.../module1/...
| '-.../module2/...
| '-framework/.../...
|- web
|- module1/.../...
|- module2/.../...
' - .../...
This was no problem in CVS (as long as each directory kept its own .cvs
folder).
Now I can't figure this out in Subversion: I have several working copies
which is bad for many reasons: All status/update/...-commands work only
"per module".
The main problem is this:
Some changes which are supposed to be ONE new revision affect more than
one module and/or the framework and/or the webspace. HOW can I do this??!
Any help would be highly appreciated. Right now I'd have to create like
8-20 different revisions and 7-19 of them would be "inconsistent"
(compile errors due to framework/module mismatch).
The only thing I can currently think of is a complete restructuring for
the repository - which would of course break any build script we've ever
created (uhh... and we'd need old scripts for old revisions and new
scripts for new revisions *headache*). And be a lot of work. And would
invalidate some working copies...
Any ideas???!
Thanks in advance,
Holger
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: no atomic commit due to layout-problems?! mixed wc...??!
Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
Ulrich Eckhardt wrote:
> On Monday 20 June 2005 21:40, Holger Stratmann wrote:
> > Some changes which are supposed to be ONE new revision affect more than
> > one module and/or the framework and/or the webspace. HOW can I do this??!
>
> svn:external, read it up in the book.
Argh. Of course this will not produce one single atomic commit (unless
Subversion does some real magic, which it indeed could). What it does is that
using externals you can reduce the whole issue to a single commit command,
but I don't think the parts thereof are committed atomically.
/me makes a note not to post serious stuff after Soulfly concerts...
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: no atomic commit due to layout-problems?! mixed wc...??!
Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
On Monday 20 June 2005 21:40, Holger Stratmann wrote:
> From the "old CVS days", we have a repository which has "modules" at
> the top of the structure.
[...]
> Now I can't figure this out in Subversion: I have several working copies
> which is bad for many reasons: All status/update/...-commands work only
> "per module".
> The main problem is this:
> Some changes which are supposed to be ONE new revision affect more than
> one module and/or the framework and/or the webspace. HOW can I do this??!
svn:external, read it up in the book.
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org