Ticket #780 (closed defect: fixed)
a directory's depth is ignored by update
|Reported by:||michael.hufer@…||Owned by:||alwin|
In a big project one does often not want to checkout every sub-directory. So the project is checked out with e.g. 'svn co --depth=immediates <myProject>' followed by a update changing the depth of some sub-folders in the project e.g. in a project with a include, libsrc, guisrc and share folder one might only want to work on the library part and thus only fetch the files needed to build it using e.g. 'svn up --set-depth=infinity libsrc include' to get all files/dirs in 'libsrc' and 'include' but not those in 'guisrc' and 'share' which are not relevant to build the lib. A subsequent 'svn up' does not change the depth of 'guisrc' and 'share' in this example and only updates 'libsrc' and 'include'.
Unfortunately kdesv does not obey the depth of a folder in the working copy (set during checkout) when updating the base folder and checks everything out with the equivalent of 'svn up --set-depth=infinity'
It seems the default depth for svn_client_update3() is always set to 'svn_depth_infinity' when kdesvn updates. This is IMHO wrong the default should be 'svn_depth_unknown' which - according to the svn API docs - will result in the expected behaviour (i.e. the same default as the svn commandline tool) and this should only be overwritten by a user setting.