RE: Mimicing CVS modules in Subversion
I'm also looking for a way, were I can tell subversion to simply check out a
module/alias to get only a subset of directories.
We have a large repository that is used to development different devices. those
devices are using sometimes the same subdirectories and sometimes different
subdirectories (e.g. driver for different hardware).
If one device supports a functionality that the other device does not, we need to
avoid checking out all directories/features.
This is because some of the developer are only working on few different hardware
platforms or for few different products.
The current repository contains about 35Gbyte. A product needs only few megabytes
of sources and libraries.
A good feature would be if we can tell svn to checkout only predefined set of
directories. At moment we create a script that checks out the toplevel directory
and runs an update on only the needed directories. But we are using about 4
different GUI tools that do not support this feature.
I have tried to create a directory with externals and could simulate modules. But
this is only handy if you have a flat structure. If you have a lot of modules and
different directories depth that you get lost in creating such modules.
Also user always have to check out from the "modules" directory instead of the
commen used trunk.
Using externals does not work for commit operations and therefore it is not usable.
Subversion should urgently support a mechanism of modules/aliases. Perhaps you can
define a property in the root directory that defines the module file describing
modules/aliases. if you use a "svn co" svn should first check for module/aliase
within that description file before checking for the directories
Perhaps this description file can also support externals.
Received on 2009-01-21 14:47:21 CET
This is an archived mail posted to the Subversion Dev