From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Various icedtea6 patches
Date: Fri, 20 Mar 2015 21:17:04 +0100 [thread overview]
Message-ID: <87a8z78lvj.fsf@gnu.org> (raw)
In-Reply-To: <idjtwxhcf43.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Thu, 19 Mar 2015 14:05:00 +0100")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> Ludovic Courtès writes:
>
>>> From 9c9ef4fde4003a3bc9af73462552edde5d46c909 Mon Sep 17 00:00:00 2001
>>> From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
>>> Date: Tue, 10 Mar 2015 14:05:48 +0100
>>> Subject: [PATCH 3/5] gnu: icedtea6: patch patches in separate build phase.
>>>
>>> * gnu/packages/java.scm (icedtea6)[arguments]: patch patches in a separate
>>> build phase `patch-patches' instead of `patch-paths'.
>>
>> Is it really patches that are being patched? Not obvious from a quick
>> look.
>
> Yes, it is patches being patched. OpenJDK comes with patches and some
> of them have to be patched (rather than the sources), because they are
> applied during the build phase, not at a point at which we could
> interject another phase.
>
> In the diff it's not very clear, but looking at the resulting phase
> after applying the patch you can see that there are only two substitute
> expressions for the following files, all patches:
>
> "patches/jtreg-jrunscript.patch"
> "patches/hotspot/hs23/drop_unlicensed_test.patch"
> "patches/openjdk/6799141-split_out_versions.patch"
Yuk, OK. Thanks for explaining.
>> Anyway, maybe “Move patching from ‘patch-paths’ to new ‘patch-patches’
>> phase.”
>
> Or maybe
>
> "Move patching of patches from ‘patch-paths’ to new ‘patch-patches’
> phase.",
>
> because it's not actually patching of sources but patching of patches?
OK!
Thank you,
Ludo'.
prev parent reply other threads:[~2015-03-20 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 13:18 [PATCH] Various icedtea6 patches Ricardo Wurmus
2015-03-19 9:07 ` Ludovic Courtès
2015-03-19 13:05 ` Ricardo Wurmus
2015-03-20 20:17 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8z78lvj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).