[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Install hook

From: pelzflorian (Florian Pelz)
Subject: Re: Install hook
Date: Sun, 19 Mar 2017 13:50:08 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.8.0

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
> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]