3rd party software customizations

[Cristiano Cortezia]

Hi all,

I am trying to figure out the best strategy to version control a third
party library, which is meant to be customized internally.

The main problem arises, of course, after the library provider releases a
new version of their code, and these changes must be mixed to the local
changes.

The "Vendor Branches" strategy purposed on the svn book (
http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.advanced.vendorbr)
seems to make sense (I have some subversion background). I'm just not sure
if this is the best approach on mercurial, or any other dvcs.

Do someone have a suggestion ? Any pointers are welcome.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20120416/6f1fc860/attachment-0002.html>