unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabian Harfert <fhmgufs@web.de>
To: guix-devel@gnu.org
Subject: Desktop variables and caches
Date: Thu, 18 Feb 2016 15:51:09 +0100	[thread overview]
Message-ID: <20160218155109.2e5a817c@alarmpi> (raw)

Hi!

While working on and testing my MATE packages I noticed the following
things:

I already mentioned this before, but it belongs here, too: Gtk+ needs
the environment variable GTK_DATA_PREFIX defined to the user profile
directory to find themes.

For GdkPixbuf it's necessary to define GDK_PIXBUF_MODULEDIR to the
sub-directory lib/gdk-pixbuf-2.0/2.10.0/loaders of the users profile to
make it finding loader modules like the one provided by librsvg for
SVG support. In addition the command 'gdk-pixbuf-query-loaders' needs
to be called to cache the different loaders. For that the variable
GDK_PIXBUF_MODULE_FILE has to contain the cache file
(lib/gdk-pixbuf-2.0/2.10.0/loaders.cache). That must be done when the
profile is built.

To allow GLib GSettings to find it's compiled settings schemas the
command 'glib-compile-schemas' with the share/glib-2.0/schemas
directory needs to be called when the profile is built.

The last two points result in the fact, that each package using
extensions to GdkPixbuf or GSettings schemas from other packages needs
to propagate them (e.g. librsvg or gsettings-desktop-schemas).

We also need to define the XDG_CONFIG_DIRS variable. It is used by
several applications to find files in etc from other applications.

Please note that I'm still not using the Guix system distribution, so I
don't know if this also applies for that platform, but I think so.

Fabian

             reply	other threads:[~2016-02-18 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 14:51 Fabian Harfert [this message]
2016-02-20  5:52 ` Desktop variables and caches Leo Famulari

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=20160218155109.2e5a817c@alarmpi \
    --to=fhmgufs@web.de \
    --cc=guix-devel@gnu.org \
    /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).