unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 26215-done@debbugs.gnu.org
Subject: bug#26215: gschemas.compiled should not be added to the profile by multiple packages
Date: Sun, 27 Dec 2020 01:26:32 +0100	[thread overview]
Message-ID: <0f63f105c38dab2bb3e4440803c50f3a5049862b.camel@student.tugraz.at> (raw)
In-Reply-To: <20201227000224.uhthhfoeaov5odni@pelzflorian.localdomain>

Hello Florian,

Am Sonntag, den 27.12.2020, 01:02 +0100 schrieb pelzflorian (Florian
Pelz):
> [...]
> 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.
Thanks for formally closing this bug.  As far as purging the files is
concerned, we do already remove GTK icon caches from packages all over
the place, that would otherwise require gtk+:bin as native input, so it
*is* an option for saving a little space here and there.  That being
said, it is not strictly necessary, just an option if anyone is
sufficiently bored.

Regards,
Leo






      reply	other threads:[~2020-12-27  0:27 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)
2020-12-27  0:26     ` Leo Prikler [this message]

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=0f63f105c38dab2bb3e4440803c50f3a5049862b.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=26215-done@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 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).