quilt for patch management?
Andrew John Hughes
gnu_andrew at member.fsf.org
Fri May 8 07:34:12 PDT 2009
2009/5/8 Robert Schuster <thebohemian at gmx.net>:
> 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'.
They all get applied as part of the build. The current target is to
remove most of them by having them pushed upstream.
> 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.
Personally, if the build fails on a patch, I reapply it against the
current sources and fix any conflicts. I have a script to speed this
up. It just greps the patch, and creates two directory trees
containing the appropriate original files form OpenJDK. I then apply
the patch to one and resolve any issues, before creating a new patch.
It may not be the most efficient way but it works for me and has been
well-tested. I'm reluctant to trust the process to a tool I don't
know very well, especially if that tool is expected to work for all
developers using IcedTea. It just seems to complicate things
The time spent switching to quilt would be better spent getting
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
More information about the distro-pkg-dev