From: Florian Pelz <pelzflorian@pelzflorian.de>
To: guix-devel@gnu.org
Subject: Re: Install hook
Date: Tue, 21 Mar 2017 21:51:19 +0100 [thread overview]
Message-ID: <1490129479.1176.1.camel@pelzflorian.de> (raw)
In-Reply-To: <71f4164b-0f83-ed0d-12b8-4618e2138e8c@pelzflorian.de>
On Tue, 2017-03-21 at 11:06 +0100, pelzflorian (Florian Pelz) wrote:
> On 03/21/2017 09:11 AM, Ricardo Wurmus wrote:
> >
> > Would you like to give it a try to add a profile hook for building
> > “gschemas.compiled” once for all packages in a given profile?
> >
>
> I’ll take a closer look at the code and try it. Since packages are
> shipped as part of Guix anyway, one profile hook in Guix maybe is not
> worse than allowing hooks to be added to e.g. the glib package in this case.
>
> > Please also email a summary to bug-guix@gnu.org so that we can keep
> > track of this.
> >
>
> Will do.
>
Sorry. I’m feeling a little stupid. GSettings checks each entry in
XDG_DATA_DIRS for a gschemas.compiled file, so compiling the settings
for each package individually does work. The issue with the app I was
trying to run was elsewhere.
Now, all GSettings could still be compiled in a profile hook to a
single gschemas.compiled file to eliminate the annoying warning message
about “arbitrarily choosing” one of them. I have seen an mlet for the
first time today, so I’m not going to fix this. I’m also not sure if
this is really better than what (guix build glib-or-gtk-build-system)
does.
I’m also not going to file a bug since I’m not sure if we even want to
change the current method.
prev parent reply other threads:[~2017-03-21 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 10:30 Install hook Florian Pelz
2017-03-19 11:23 ` John Darrington
2017-03-19 12:14 ` Julien Lepiller
2017-03-19 12:50 ` pelzflorian (Florian Pelz)
2017-03-19 13:14 ` John Darrington
2017-03-19 13:41 ` pelzflorian (Florian Pelz)
2017-03-21 2:03 ` John Darrington
2017-03-21 8:11 ` Ricardo Wurmus
2017-03-21 10:06 ` pelzflorian (Florian Pelz)
2017-03-21 20:51 ` Florian Pelz [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1490129479.1176.1.camel@pelzflorian.de \
--to=pelzflorian@pelzflorian.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 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.