SVN: vendor branches + patch + history?

Question

We have a rather large library that we need to periodically import (and then fix) into our code base.

The SVN book apparently recommends a “vendor branch” scheme where we save our revised version of the “vendors”. This will work, except that the provider also uses SVN and gives us read access to reuse them.

It would be great to have access to the supplier file history when we need to update our patches.

So my question is:

Is there a way to have a fixed provider branch that also somehow preserves access to history for the provider files?

(I saw the mention of svn: external folders, but I'm not sure I really understand the full consequences in terms of linking the revision and how exactly we will support our own patches against this.)

What is the correct route? (FWIW, the supplier issues once a month. We intend to pull out updates once / twice a year.)

thank

Answer 1

Well, here you are, please, the source of the supplier along with the story, but you also apply your patch to the source of the supplier. Getting a source with a story is easy. Getting their source with a story and then applying your corrections and constantly doing it is difficult.

, , ( , ), , .

, , svnsync . Svnsync - - . svnsync , . .

, , svnsync. , .

, . /.

, . , .

, , , svn: external, . , , .