From: Ricardo Wurmus <rekado@elephly.net>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guix-devel@gnu.org
Subject: Re: Install hook
Date: Tue, 21 Mar 2017 09:11:19 +0100 [thread overview]
Message-ID: <87d1dbf3rs.fsf@elephly.net> (raw)
In-Reply-To: <a5c884df-fc6f-cc04-706d-dc773819116b@pelzflorian.de>
pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> writes:
> 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 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.
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?
Please also email a summary to bug-guix@gnu.org so that we can keep
track of this.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-03-21 8:11 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1dbf3rs.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@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.