On Wed, Aug 09, 2006 at 06:53:08AM -0700, Russ Allbery wrote:
> Ian Jackson <[EMAIL PROTECTED]> writes:
[...]
> > Note that there are ways of dealing with the situation you describe
> > above which don't break the standard model.  For example, you could have
> > the .diff.gz specify the _patched_ source and store the patches
> > separately in debian/patches.  Every diff would appear twice but this is
> > not usually a big problem.  Someone who didn't know about your patch
> > system would just produce a working package and a reasonable diff to
> > send to the BTS (if it's not just a local change), and you as maintainer
> > can do the patch system integration when you include it.
> 
> That's an interesting idea.  I can't see an obvious problem with it after
> a few minutes of thought, other than making it a bit harder to deal with a
> quilt-using package inside a revision control system, and that could be
> automated.

I tried months ago but failed, so I am very interested if someone has
a clean solution.

Denis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to