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: GSettings schemas
Date: Thu, 11 Feb 2016 23:29:40 +0100	[thread overview]
Message-ID: <20160211232940.68101278@alarmpi> (raw)

Hi!

Trying to use some successfully built packages I noticed that they fail
to start because of missing installed GSettings schemas. When the
profile is build, each package, that has a gschemas.compiled file in
its share/glib-2.0/schemas/ directory overides the one of the last
package so that lots of schemas are missing.

I think it would be enough to just call 'glib-compile-schemas' with the
profile output directory as an argument after all packages are in the
profile, where their XML schema files live in share/glib-2.0/schemas/.
That would generate one gschemas.compiled for all of them.

WDYT?

Fabian

             reply	other threads:[~2016-02-11 22:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 22:29 Fabian Harfert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-13 13:13 emacs package Federico Beffa
2014-09-15  7:55 ` Ludovic Courtès
2014-09-16  7:38   ` Federico Beffa
2014-09-16 20:04     ` Federico Beffa
2014-09-17  9:11       ` Ludovic Courtès
2014-09-17 16:57         ` Federico Beffa
2014-09-18 12:01           ` Ludovic Courtès
2014-09-18 18:37             ` Federico Beffa
2014-09-19  7:54               ` Ludovic Courtès
2014-09-19 17:13                 ` Federico Beffa
2014-09-20 13:20                   ` Ludovic Courtès
2014-09-20 19:57                     ` Federico Beffa
2014-09-20 20:28                       ` Ludovic Courtès
2014-09-20 22:02                         ` Federico Beffa
2014-09-22  7:38                           ` GSettings schemas Ludovic Courtès
2014-09-23 18:39                             ` Mark H Weaver

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=20160211232940.68101278@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).