Hi,
I have to develop software tools that allow users
to check out specific parts of a directory tree.
For example, there is
http://server/repository/product/trunk/dira/dirb
Users want one script that sets up their environment,
so it would create an empty directory wc, containing an
empty directory dira, containing an empty directory dirb.
They want this structure to be set up so they can later
decide what specific source files to work on.
They want a second script that populates the structure.
Ideally with single files. If, for example, there is a
file b.cpp in http://server/repository/product/trunk/dira/dirb,
they want to say "checkout b.cpp" in any subdirectory
(wc, dira, or dirb) and the script must find out that
it needs to put b.cpp into wc/dira/dirb.
I know the easiest way to implement that would be to
simply let the first script check out everything and
then remove everything except for the hidden .svn
directories. The second script must then use "svn list -R"
on the base directory to find out where the needed file
goes and, in the above example, issue an "svn update b.cpp"
in wc/dira/dirb.
The problem with checking out everything an then deleting
most of it is obvious: I am wasting a lot of bandwith and
people (like me) who only have a 64kbit ISDN line have to
wait forever.
Obviously, I could let my script create fake ".svn"
directories, but that does not seem right, as the
structure inside them is subject to change.
Is there a correct way of doing this?
Thanks!
Carsten.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 27 20:01:02 2005