Re: tracking multiple 3rd-party sources

On Sat, Dec 18, 2004 at 12:01:04PM -0500, Robert P. J. Day wrote:
>
> so, the normal progression for a single piece of 3rd party software
> might be, for example:
>
> 3.0 (original pristine version that we started with)
> 3.0 + a local patch
> 3.0 + another local patch
> 3.0 + a third local patch
> 3.1 (start from scratch again, might not need any local patches)
> 3.1 + the previous second local patch (if it turns out we still
> need it even for 3.1)

It may be that the best approach for this is an external patch manager,
with the pristine sources and the patches stored in subversion. Part of
the build process would be applying the patches.

A patch manager used by some of the Linux kernel maintainers is 'quilt':

http://savannah.nongnu.org/projects/quilt/

Here's a basic tutorial:

https://wiki.clusterfs.com/lustre/KernelPatchManagement

If you're using Debian: apt-get install quilt

Steve

-- 
"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org