From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gtk+: Support GUIX_GTK{2,3}_PATH variables.
Date: Tue, 08 Dec 2015 21:25:45 +0100 [thread overview]
Message-ID: <87poygn0vq.fsf@elephly.net> (raw)
In-Reply-To: <87k2oui80q.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> From 11f502281064525a067c1453cd2b7b663bf6c3bb Mon Sep 17 00:00:00 2001
>> From: Ricardo Wurmus <rekado@elephly.net>
>> Date: Thu, 3 Dec 2015 08:32:06 +0100
>> Subject: [PATCH 2/3] gnu: gtk+: Add patch to support GUIX_GTK3_PATH.
>>
>> * gnu/packages/patches/gtk3-respect-GUIX_GTK3_PATH: New file.
>> * gnu-system.am (dist_patch_DATA): Add it.
>> * gnu/packages/gtk.scm (gtk+) [source]: Add patch.
>> [native-search-paths]: Add search path for GUIX_GTK3_PATH.
>
> LGTM.
>
> This will have to go to a separate branch. We’ll get Hydra to build it
> once it’s done with the security updates.
Could you push them to a new branch then? I have no control over what
Hydra builds and I assume you’d want to rebase them on top of the
security updates.
> I agree with Andy that this needs to be discussed with upstream though.
> Could you open a bug on their tracker and explain the problem and
> proposed solution?
Yes, I’ll take care of this.
~~ Ricardo
next prev parent reply other threads:[~2015-12-08 20:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 7:52 [PATCH] gtk+: Support GUIX_GTK{2,3}_PATH variables Ricardo Wurmus
2015-12-03 10:01 ` Andy Wingo
2015-12-03 21:59 ` Ricardo Wurmus
2015-12-04 9:13 ` Andy Wingo
2015-12-04 14:49 ` Ludovic Courtès
2015-12-08 20:25 ` Ricardo Wurmus [this message]
2015-12-09 13:53 ` Ludovic Courtès
2015-12-25 11:16 ` Ricardo Wurmus
2015-12-29 1:10 ` Mark H Weaver
2015-12-30 3:23 ` Mark H Weaver
2015-12-30 16:20 ` Ludovic Courtès
2015-12-31 11:27 ` Ricardo Wurmus
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=87poygn0vq.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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).