I have a variation on a problem discussed in another thread with the
I would like to start using Subversion for projects with a directory
structure that looks something like this (structure has been simplified
The problem is this: many of the users would like to be be able to check
out the directory tree and work with the source files at level 4 of the
directory structure, but they may not wish to see the level_4b_dir
directories. In fact, the binary files in level_4b_dir directories are
large enough to cause disk space problems for many users if they were to
be all checked out at once.
What I would like to do is somehow hide the level_4b_dir directories
from users that wish to hide these directories.
Solutions I have considered:
1. Create a revisioned directory tree with the same structure as one above
and use svn:externals propreties to populate the level_3x_dir
directories with level_4a_dir.
2. Create a script that creates a local un-revisioned directory tree
that looks like the one above and use svn checkout to populate
the level_3x_dir directories with level_4a_dir.
3. Checkout the whole directory tree, and then remove the directories
the user does not wish to see.
What I don't like about solutions 1 and 2 is that making changes at the
level_3x_dir level and above becomes tricky and non-obvious to users
that are not svn savvy. Changes to the mirror won't be reflected in the
main trunk. Commits will not work recursively. The "mirrored" directory
trees would have to be maintained somehow.
Solution 3 seems simpler, but some users may run into disk space issues
before the unwanted directories can be deleted.
What do you think, svn users, is there some other way I can tackle this?
Any discussion would be welcome.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jul 29 00:39:31 2004