Re: Brasero, or gnome without gnome

[Andreas Enge <andreas@enge.fr>]

On Thu, Oct 03, 2013 at 12:17:39AM +0200, Ludovic Courtès wrote:
> Do you mean a solution that does not require any action upon
> installation?  That would at least require using different file names
> than just ‘gschemas.compiled’, no?

Yes. I also wondered if these were needed; one could imagine that this
compilation step would just be a caching mechanism, and that things still
work if the uncompiled original xml files are present. But this does not
seem to be the case as far as I can tell from my tests - brasero insists on
its xml file having been compiled into gschemas.compiled. And this is also
what happens in debian.

> 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"?

Andreas