From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 26215-done@debbugs.gnu.org, 26215@debbugs.gnu.org
Subject: bug#26215: gschemas.compiled should not be added to the profile by multiple packages
Date: Sun, 27 Dec 2020 01:02:24 +0100 [thread overview]
Message-ID: <20201227000224.uhthhfoeaov5odni@pelzflorian.localdomain> (raw)
In-Reply-To: <2df15184d0776c75bb37052bd40f76b59e742e95.camel@student.tugraz.at>
Hello Leo! Thank you for going through old issues!
So the issue appears to be fixed by commit
de136f3ee7878dea139e751b7e4ca04c2542c91d (from year 2018) making sure
a gschemas.compiled encompassing all packages in a Guix profile gets
created. Reverting that commit does not print warnings today (I don’t
know why), but still causes choosing one of the packages’
gschemas.compiled over the other.
For normal usage, creating individual, per-package gschemas.compiled
files in glib-or-gtk-build-system probably is *useless*. Checking the
utility is hard though because I have not found a package that does
not create a per-package gschemas.compiled in their build phase
anyway.
I think the bug is done. Purging the gschemas.compiled files from all
packages would need to be done in an extra phase for many build
systems (glib-or-gtk build system, cmake build system, meson build
system) that would be useless when a package does not use glib. It is
difficult. Also the gschemas.compiled files are small in size. Some
people maybe even do or could rely on the per-package
gschemas.compiled file in self-written setups that do not use Guix
profiles/environments.
Closing.
Regards,
Florian
next prev parent reply other threads:[~2020-12-27 0:03 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
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) [this message]
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
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=20201227000224.uhthhfoeaov5odni@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=26215-done@debbugs.gnu.org \
--cc=26215@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).