tony mancill writes: > On Fri, 30 Jul 1999, David Coe wrote: > Having made the mistake of applying the patches to the source tree and > then having to jump through major hoops everytime a new upstream version > came out, I think that you are on the right track. I have a directory in > the root of my package directory named non_upstream which I use for things > that the upstream people will not incorporate into their source and are > required to comply with the FHS, etc. But I normally just copy the new > versions into place during the build. If you apply them as patches, > you'll need to remember to revert them during your "make clean" phase. > > It might be sort of nice to do it the way you propose, but I'd like to > hear some other thoughts on the matter.
Have a look at the egcs (soon gcc) source packages. For each patch an executable script debian/patches/<name>.dpatch exists. All patches are applied and unapplied in the debian/rules file at build/clean time. Have a look. The libc6 maintainer reworked (?) this patch rules, so you could look at it too.
