svn-externals with own svn-externals: how to recursively checkout? -
so i'm using svn:externals checkout external repo. external repo has own svn-externals set up.
now, when updating working copy of project, files external repo being updated, externals not. behavior designed, can extended update external dependencies?
recursive checkout supported since subversion1.5, thread illustrates.
the "version control subversion" book mention svn checkout, svn update, svn switch, , svn export commands able recurse in externals repos, but:
- if external set particular revision, no amount of '
update' change file in it, though external repo has had new revisions. - the update must initiated parent repo, not directly sub-repo:
be careful, though, don't inadvertently modify external working copy in subtle ways cause problems.
example, while externals definition might specify external working copy should held @ particular revision number, if runsvn updatedirectly on external working copy, subversion oblige, , now external working copy out of sync declaration in primary working copy.
so maybe 1 of 2 cases applied here.
the op carsten reports:
it working now.
i had set externals prop on root node of external project (lets project '
lib').
in concrete project (project 'a'), external defined on sub-folder of 'lib' (ie.mylocalfolder > lib/somefolder).
seems reason subversion not recursinglib's externals; looked inside 'somefolder', didn't find external defs there, didn't checkoutsomefolder/externallib.
now, in 'lib' changed externals definitions defined inside folder refer in 'a'; works charm now!
Comments
Post a Comment