From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: [PATCH] gtk+: Support GUIX_GTK{2,3}_PATH variables. Date: Wed, 09 Dec 2015 14:53:55 +0100 Message-ID: <87si3bsp70.fsf@gnu.org> References: <877fkwotnw.fsf@elephly.net> <87bna7g8a2.fsf@igalia.com> <87wpsvnqhe.fsf@elephly.net> <87k2oui80q.fsf@gnu.org> <87poygn0vq.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42896) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a6fBy-00042E-LC for guix-devel@gnu.org; Wed, 09 Dec 2015 08:54:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a6fBu-0002JB-6Q for guix-devel@gnu.org; Wed, 09 Dec 2015 08:54:02 -0500 In-Reply-To: <87poygn0vq.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 08 Dec 2015 21:25:45 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ricardo Wurmus Cc: guix-devel Ricardo Wurmus skribis: > Ludovic Court=C3=A8s writes: > >> Ricardo Wurmus skribis: >> >>> From 11f502281064525a067c1453cd2b7b663bf6c3bb Mon Sep 17 00:00:00 2001 >>> From: Ricardo Wurmus >>> 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=E2=80=99ll get Hydra to b= uild it >> once it=E2=80=99s 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=E2=80=99d want to rebase them on top of the > security updates. Here=E2=80=99s the deal: If you push a new branch based on current master, = I=E2=80=99ll make sure Hydra builds it. :-) >> 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=E2=80=99ll take care of this. Awesome, thanks! Ludo=E2=80=99.