unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: IBus and different GTK versions
Date: Tue, 15 Sep 2015 21:16:55 +0200	[thread overview]
Message-ID: <87twqv7as8.fsf@elephly.net> (raw)
In-Reply-To: <CAHZE2pdJs9yL2yLw42fnLz6PgNsW7t3CB4=kvwN=XnS5_mSX7g@mail.gmail.com>


宋文武 <iyzsong@gmail.com> writes:

>>> We can set 'GTK_EXE_PREFIX' to the '~/.guix-profile', and generate the
>>> 'immodules.cache' files in a profile hook.  It will work for both gtk2
>>> and gtk3 applications.

>> Does this mean that GTK needs to be installed in the user’s profile for
>> this to work?  I thought ‘GTK_EXE_PREFIX’ would change the path of
>> ‘$libdir’ for *all* of GTK’s libraries.  It can only have one value, not
>> a list of paths to look for libraries.

> Yes, this require install GTK+ into user's profile.
> Also, there is a 'GTK_DATA_PREFIX' in a same situation, which I think is
> the only way to set the GTK+ 2 theme.

Isn’t this a little too high a price to pay?  One can only install one
(major) version of GTK+ into a profile, so when we begin propagating the
GTK inputs users will run into conflicts.

I would really like to avoid propagating GTK+ (although it may be a bad
idea to have software depend on different minor versions of GTK+).  It
would be very nice if only additional modules—such as explicitly
installed themes and input method modules—would have to be installed to
the profile.  Those who do not need themes or input methods would not
need to be bothered with this at all.

~~ Ricardo

  reply	other threads:[~2015-09-15 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13 11:27 IBus and different GTK versions Ricardo Wurmus
2015-09-13 11:51 ` 宋文武
2015-09-14  8:06   ` Ludovic Courtès
2015-09-14  8:28   ` Ricardo Wurmus
2015-09-14  9:18     ` 宋文武
2015-09-15 19:16       ` Ricardo Wurmus [this message]
2015-09-20 17:12         ` Ricardo Wurmus
2015-09-20 18:25           ` Ricardo Wurmus
2015-09-21 16:06             ` Ludovic Courtès

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=87twqv7as8.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@gmail.com \
    /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).