unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gtk+: Support GUIX_GTK{2,3}_PATH variables.
Date: Fri, 04 Dec 2015 09:13:30 +0000	[thread overview]
Message-ID: <87h9jyefut.fsf@igalia.com> (raw)
In-Reply-To: <87wpsvnqhe.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 03 Dec 2015 22:59:09 +0100")

On Thu 03 Dec 2015 21:59, Ricardo Wurmus <rekado@elephly.net> writes:

>> Andy Wingo <wingo@igalia.com> writes:
>>
>> Only question for me would be, would these patches with s/GUIX_// be
>> accepted upstream?  They should be submitted at least.
> 
> I haven’t tried and I don’t really know how to present it.  For
> FHS-abiding distributions this is not a problem usually, because
> GTK_EXE_PREFIX could be used instead.  We cannot set GTK_EXE_PREFIX to
> ~/.guix-profile/lib because that would make it necessary for ibus (for
> example) to propagate the gtk+ package, which is unacceptable for us.
> 
> I think FHS people simply have no need for it.

ACK.  In that case LGTM FWIW.  I wonder what Nix does here, but that's
just idle wondering :)

Cheers,

Andy

  reply	other threads:[~2015-12-04  9:14 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 [this message]
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
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=87h9jyefut.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).