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
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 ho
pelzflorian (Florian Pelz) 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
On Sun, Mar 19, 2017 at 02:41:09PM +0100, pelzflorian (Florian Pelz) wrote:
No, normally gschemas.compiled is one file storing information about all
GSettings application. It must thus be created from files provided by
multiple packages.
For example, gnome-calculator ship
On 03/19/2017 02:14 PM, John Darrington wrote:
> The problem as I understand it is as follows:
>
> Two (or more) packages both contain a file: /gnu/store/.../xyz/foo
>
> So long as those two packages are not both installed into the same profile at
> the same time, this is not a problem. However
The problem as I understand it is as follows:
Two (or more) packages both contain a file: /gnu/store/.../xyz/foo
So long as those two packages are not both installed into the same profile at
the same time, this is not a problem. However if the user chooses to
install both packages concurrently,
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
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-
Hello Florian,
I agree that this is a problem. It has been discussed before, and various
solutions have been suggested, but I don't think install hooks was one of
them.
Can you elaborate on your idea? What would an install hook do, and how would
it work?
J'
On Sun, Mar 19, 2017 at 11:30:48A
