unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gtk+: Support GUIX_GTK{2,3}_PATH variables.
Date: Wed, 30 Dec 2015 17:20:18 +0100	[thread overview]
Message-ID: <87y4cbrjr1.fsf@gnu.org> (raw)
In-Reply-To: <8737ukobzm.fsf@netris.org> (Mark H. Weaver's message of "Tue, 29 Dec 2015 22:23:57 -0500")

Mark H Weaver <mhw@netris.org> skribis:

> Mark H Weaver <mhw@netris.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Ludovic Courtès <ludo@gnu.org> writes:
>>>
>>>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>>>
>>>>> 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.
>>>>
>>>> Here’s the deal: If you push a new branch based on current master, I’ll
>>>> make sure Hydra builds it.  :-)
>>>
>>> I rebased the patches on top of current master and pushed them to a
>>> new branch “gtk-path-patch”.
>>
>> I just rebased them again, and started Hydra building the branch.
>>
>> http://hydra.gnu.org/jobset/gnu/gtk-path-patch
>
> This is now sufficiently built to merge to 'master', but I'm not sure
> whether it was decided to do this before getting feedback from upstream.

I think there was consensus that this is OK to install the patch for our
purposes, and that we can always adjust should upstream propose
something different.

Ricardo?

Thanks,
Ludo’.

  reply	other threads:[~2015-12-30 16:20 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
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 [this message]
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=87y4cbrjr1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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).