Questions about Subversion
From: Emmanuel Blot <c-Emmanuel.Blot_at_smart-fusion.com>
Date: 2002-02-25 18:51:06 CET
Hi,
I just discovered the Subversion project, surfing from Google.
I'm not sure to understand how far Subversion takes over CVS:
***[[A]]****
A project have a module 'A', let's call it a library, that contains a bunch of files:
The same project have a module 'B', that contains another bunch of files:
Finally, the project contains a main module 'X', that contains another bunch of files and relies on both the previous modules:
Each module (A, B, X) can have different revisions (file revisions AND module revision). For instance, X.2 may link with A.3 and B.5, but won't link with an older version of B.
CVS does not handle this kind of trouble, as it can associate files into modules, but cannot associate and handle revisions of modules themselves.
Does Subversion better handle this case than CVS does ?
*** [[B]] ***
The first module would be a (fake) audio driver:
javax.multimedia.driver.audio.* (Java files would stands in javax/multimedia/driver/audio)
another project would be a (fake) video driver:
javax/multimedia.driver.video.* (Java files would stands in javax/multimedia/driver/video)
finally, a driver manager may stand in the same 'top' package:
It would be nice to have three different 'modules' managed by the CVS system (audio.*, video.*, Manager), but only one common tree on the local disks:
javax/
CVS does not handle this king of file structure.
Does Subversion address this issue ?
Thanks in advance for your answer(s)
Regards,
---------------------------------------------------------------------
|
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.