unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Gerwitz <mtg@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Missing fonts issue with GNU Icecat
Date: Fri, 28 Dec 2018 22:58:51 -0500	[thread overview]
Message-ID: <87wont0yro.fsf@gnu.org> (raw)
In-Reply-To: <878t094rmn.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 28 Dec 2018 16:07:12 +0100")

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

On Fri, Dec 28, 2018 at 16:07:12 +0100, Ricardo Wurmus wrote:
>> ```
>> The following environment variable definitions may be needed:
>>   export
>> XDG_DATA_DIRS="$HOME/.guix-profile/share${XDG_DATA_DIRS:+:}$XDG_DATA_DIRS"
>>   export
>> GIO_EXTRA_MODULES="$HOME/.guix-profile/lib/gio/modules${GIO_EXTRA_MODULES:+:}$GIO_EXTRA_MODULES"
>> ```
>
> I’m glad you figured this out.  I wonder if this means that we should
> change the icecat package to set these variables (e.g. by adding a shell
> wrapper).

Only XDG_DATA_DIRS (or XDG_DATA_HOME) are needed for me in a
container.  Is GIO_EXTRA_MODULES actually needed for anything?  I don't
even have a `lib/gio' directory in my profile.

> What do others think?

Yes, please.  IceCat is effectively completely broken without this on
foreign distros and within containers.  It looks like on GuixSD
XDG_DATA_DIRS is set in /etc/profile; I never had to set it manually.

But the presence in /etc/profile implies to me that there are other
packages that require this variable to be present.  Should those
packages also have wrapper scripts?

-- 
Mike Gerwitz

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2018-12-29  4:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27 10:54 Missing fonts issue with GNU Icecat Daniel Gerber
2018-12-27 13:43 ` Daniel Gerber
2018-12-28 15:07   ` Ricardo Wurmus
2018-12-29  3:58     ` Mike Gerwitz [this message]
2019-01-05 17:52     ` Ludovic Courtès
2018-12-29  3:51   ` Mike Gerwitz

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=87wont0yro.fsf@gnu.org \
    --to=mtg@gnu.org \
    --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).