Andreas Enge <andr...@enge.fr> skribis: > On Thu, Oct 03, 2013 at 12:17:39AM +0200, Ludovic Courtès wrote:
[...] >> What I had in mind is that upon installation in the user’s profile, the >> glib-compile-foobar command would be run for all the schema-providing >> packages to appear in the new profile. > > This could even be done automatically without specifying it in the package > description whenever a package contains a file in share/glib-2.0/schemas/. > The glib-compile-schemas (there is also glib-compile-resources) is part of > the glib package, so should be available as an input to such a package. > But which glib version would we choose then when constructing the user > profile? Different installed packages could have different glibs as inputs, > for instance. The one that is "current" in the sense that it would be > installed by "guix package -i glib"? Assuming the format is stable, we could just use the current glib. If that’s not the case, we can always come up with a more sophisticated approach. Ludo’.
