Stefan Sperling wrote:
On Mon, Nov 04, 2013 at 11:16:12AM +0100, OBones wrote:
Hello,
When using the update command with subversion 1.8, one can set the sticky
depth with the --set-depth option.
When changing from emtpy to infinity, all the files that were not retrieved
yet are retrieved immediately.
While this is fine in most cases, I am in a situation where I'd like to
prepare the working copy setting the depths but would like to have the files
retrieved later on when doing an option-less update.
To sum up, based on svnbook sparse dirs example, here is what I'd like to be
able to do:
$ svn checkout file:///var/svn/repos mom-empty --depth empty
Checked out revision 1.
$ svn update --set-depth infinity --record-only mom-empty/daughter
Updating 'mom-empty/daughter': depth recorded
$ svn update mom-empty
Updating 'mom-empty':
A mom-empty/daughter
A mom-empty/daughter/granddaughter1
A mom-empty/daughter/granddaughter1/bunny1.txt
A mom-empty/daughter/granddaughter1/bunny2.txt
A mom-empty/daughter/granddaughter2
A mom-empty/daughter/fishie.txt
Is this something that can be done? If yes, how can I achieve this?
Thanks for your help
Perhaps this can help you:
https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/svn-viewspec.py
Thanks for this, but it won't help much in this case.
Basically, I'd like to prepare a working copy for a system that will do
the final svn update and over which I have no control. As a result, I'd
like to avoid, if possible, that this final update does nothing.
It seems it's not possible easily however, so I guess I'll have to live
with that useless update...
