From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: guix-devel@gnu.org
Subject: Re: Install hook
Date: Sun, 19 Mar 2017 13:50:08 +0100 [thread overview]
Message-ID: <a5c884df-fc6f-cc04-706d-dc773819116b@pelzflorian.de> (raw)
In-Reply-To: <20170319131437.00d9608e@polymos.lepiller.eu>
On 03/19/2017 01:14 PM, Julien Lepiller wrote:
> I think install hooks are scripts run after each package installation,
> that are provided by the package itself. We already have a similar
> mechanism that takes place when building the user's profile. See
> http://git.savannah.gnu.org/cgit/guix.git/tree/guix/profiles.scm.
> For instance, we build a icon-theme.cache cache file for every icon
> theme in the user's profile.
>
> I have seen references to gschemas.compiled in our
> gtk-or-glib-build-system. Currently we build the file in each package,
> which means that only one version will be present in the user's profile
> if they install more that one package containing this file. I believe
> gschemas.compiled contains important information about some graphical
> packages, and in our current system, only one package can be referenced
> that way.
>
> I think we should make sure that this file is never present in the
> output of a package, and add a function to build it in profiles.scm.
>
> Does it make any sense?
>
Yes, exactly. These profile hooks look similar to what I meant.
next prev parent reply other threads:[~2017-03-19 12:50 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) [this message]
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
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=a5c884df-fc6f-cc04-706d-dc773819116b@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 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).