> > utils/
> > calc/
> > calc-dev/
> > calc-some-branch-dev/
> > calc-some-tag/
> > (...)
Imagine now:
- we use it for real work for some time, so we have 100 or more
tags
- some poor guy does
svn co utils/calc
- he gets those 100 copies filling half of his hard drive
Of course we can require the poor people to use
svn co utils/calc/calc-dev
but in real we happen to have not one, not two, but rather 50 or
150 modules and writing
svn co libs/libtext/libtext-dev
svn co libs/libtcpip/libtcpip-dev
snv co libs/libthread/libthread-dev
(... repeat, repeat, repeat....)
is rather tedious comparing to running
svn co trunk/libs
to get the current package of the developed libraries...
In fact, we touch here some problem which subversion docs does
not seem to address - while subversion can make directory
copying, renaming, moving and cloning cheap, it is only cheap on
the server side. Copying, renaming, moving and cloning on client
side *is* expensive. You can have 50 developers of which
everyone must reogranize his working copy, recompile etc every
time you do something with repository structure...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 12 14:53:15 2004