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

no atomic commit due to layout-problems?! mixed wc...??!

From: Holger Stratmann <tigris_at_finch.de>
Date: 2005-06-20 21:40:21 CEST

Hi everybody,

I had a really hard time finding a good subject line and I'm afraid I
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

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,


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 20 21:42:51 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.