From: Federico Beffa <beffa@ieee.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 26215@debbugs.gnu.org
Subject: bug#26215: gschemas.compiled should not be added to the profile by multiple packages
Date: Thu, 23 Mar 2017 17:20:57 +0100 [thread overview]
Message-ID: <8760j0nevq.fsf@lupo.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <aa0dccec-4541-25af-9606-9485aae0ceb4@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Wed, 22 Mar 2017 09:30:37 +0100")
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> Currently multiple packages contain the file
> share/glib-2.0/schemas/gschemas.compiled (which is built by
> glib-or-gtk-build-system). Doing so *works* (because each package’s
> share directory in the Store is part of the XDG_DATA_DIRS environment
> variable, GSettings looks for settings in each of the gschemas.compiled
> files in the Store) but leads to *warnings* because only one package’s
> gschemas.compiled can be added to the profile at the same time.
>
> To avoid these misleading warnings, either
> · no package’s gschemas.compiled should go to the profile on
> install *or*
> · gschemas.compiled should not be created for each package by
> glib-or-gtk-build-system, instead it should be created only once
> in each profile by a profile hook from the GSettings data of all
> packages in the manifest,
> · or something else?
Note that if you mix GTK-2 and GTK-3 schemas many applications will
crash. The glib-or-gtk-build-system tries to avoid mixing the two.
Fede
next prev parent reply other threads:[~2017-03-23 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 8:30 bug#26215: gschemas.compiled should not be added to the profile by multiple packages pelzflorian (Florian Pelz)
2017-03-23 16:20 ` Federico Beffa [this message]
2017-03-23 19:25 ` pelzflorian (Florian Pelz)
2017-03-24 7:28 ` Federico Beffa
2020-12-22 20:49 ` Leo Prikler
2020-12-27 0:02 ` pelzflorian (Florian Pelz)
2020-12-27 0:26 ` Leo Prikler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760j0nevq.fsf@lupo.i-did-not-set--mail-host-address--so-tickle-me \
--to=beffa@ieee.org \
--cc=26215@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.