[svk-users] vendor branch management

[Jesse Vincent]

so say i have a project that relies on various vendor libs and i have
it laid out like this

/ <- project top level dir
   foo/ <- my code
   bar/ <- my code
   vendor <- dir for other people's code
     baz/ <- other people's code
     foo2/ <- other people's code

and baz and foo2 are accessible via svn checkouts.

normally i could use svn externals to get to those, but i want a
little more control over which svn version to get, whether to
automatically take updates, etc.

i've been using piston (http://piston.rubyforge.org/), but they
suggest that one can use svk for this.  piston basically manages
exporting a specific version to your local branch, and then lets you
update it.  the version you export is committed locally, so if you
update to a new version and find problems you can just stay with the
current version.

how would one replicate this sort of behavior in svk?

-faisal

_______________________________________________
svk-users mailing list
svk-users at lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-users