3rd party software customizations

[Arne Babenhauserheide]

Hi Cristiano,

Am Montag, 16. April 2012, 21:29:08 schrieb Cristiano Cortezia:
> 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.

I did that once and I used a simple vendor-branch. Every new release landed in 
the vendor branch and got then merged into default. The main problem was, that 
I sometimes got conflicts between my own changes and upstream changes. But 
that can’t really be avoided…

If the upstream library has a Mercurial repository, I would rather use a 
personal branch for my changes and leave the upstream repo structure intact. 

Best wishes,
Arne
--
singing a part of the history of free software: 

- http://infinite-hands.draketo.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20120417/b30158e8/attachment.asc>