version control - SVN: Vendor branches + patching + history? -

we have rather large library need periodically import (and patch) our code base.

the svn book seems reccomend "vendor branch" scheme keep our patched version of "vendor drops". work, except vendor uses svn , gives read access reop.

it great have access history of vendor files when need update our patches.

so question is:

is there way have patched "vendor branch" somehow keeps access history vendor files?

(i've seen mention of svn:external folders, i'm not sure understand full ramifications in terms of pegging revision, nor how maintain our own patches against that.)

what correct route take here? (fwiw, vendor releases once month. intend pull updates once/twice year.)

thanks

okay, here's rub, want vendor's source along history, apply patch vendor's source. getting source history easy. getting source history , applying patches , continually this, tough.

now assuming don't place vendor's source directory source (meaning build 2 projects separately), have couple of options if keep 2 source in separate repositories.

if wanted vendors source along history, can set svnsync vendors repository , pull changes on regular interval. svnsync wonderfull way remotely local copy complete set of history. 1 caveat svnsync is repository becomes read-only. cannot apply patch source.

now, since once or twice year, go through process of pulling down new copy of repository using svnsync. break sync , make copy of vendor's repo writable , apply patches.

the other option have vendor dump of repo , send you. load dump own repository , make read/write.

with either option, you'll have reapply patches copy of vendor's repository every time go through process. @ least once or twice year.

now, if have have source in source, still above, use svn:external noted in question. you'll still need apply patches need make vendor's source copy of vendor's repository.