Ludovic Courtès <[email protected]> writes: > Ricardo Wurmus <[email protected]> skribis: > >> Ludovic Courtès <[email protected]> writes: >> >>> Ricardo Wurmus <[email protected]> skribis: >>> >>>> From 11f502281064525a067c1453cd2b7b663bf6c3bb Mon Sep 17 00:00:00 2001 >>>> From: Ricardo Wurmus <[email protected]> >>>> 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 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. My email to [email protected] is still awaiting moderation :-/ Maybe I should try again after subscribing. ~~ Ricardo
