quilt for patch management?

Andrew Haley aph at redhat.com
Fri May 8 07:27:36 PDT 2009


Robert Schuster wrote:

> Andrew Haley schrieb:
>>> If someone wants to investigate manually quilt push/pop are there.
>>>
>>> Is this something you IcedTea developers would be interested in?
>> You haven't really explained what the point of this is.

> My point is that this would make updating and integrating single patches
> easier. I don't know how you do this currently. As there is no special
> makefile rule for applying/removing a single patch I assume you do this
> manually which is IMHO more cumbersome than issueing 'quilt push' or
> 'quilt pop'.

OK.  Why is it better to do

patch -p0 < <patch>

or

quilt import -p0 <patch>

I don't get it.  Seriously, I'm baffled: how would it make any difference?

> Furthermore how do you update a patch at the moment? Manually as well?
> quilt has a refresh command for this. It basically works like a poor man
> SCM sandbox.

Updating patches is probably a bad thing.  It makes more sense to apply
the patch and your changes to pristine sources and regenerate.

Andrew.



More information about the distro-pkg-dev mailing list