Re: Brasero, or gnome without gnome

[Ludovic Courtès]

Andreas Enge <address@hidden> skribis:

> On Wed, Oct 02, 2013 at 02:41:46PM +0200, Andreas Enge wrote:
>> How can we get around running commands such as
>>    /usr/bin/glib-compile-schemas --allow-any-name 
>> /usr/share/glib-2.0/schemas/ ?
>
> It appears that glib-compile-schemas is called during the build or 
> installation
> process of brasero.
>
> Inside /nix/store/...brasero/share/glib-2.0/schemas,
> there is a file org.gnome.brasero.gschema.xml, which has been compiled into
> gschemas.compiled. So this gschemas.compiled is installed into the user
> profile, and with the following line added to .bashrc:
>    export XDG_DATA_DIRS=$HOME/.guix-profile/share
> it is found and brasero starts up.

Oh, good that you found it.

Is there a more specific environment variable that could be put in
‘native-search-paths’ (so that ‘guix package --search-paths’ gives the
right hint)?

> Of course, this works only as long as only one gnome program is installed,
> since all the different gschemas.compiled step on each other's toe.

They’re all called ‘gschemas.compiled’?

If yes, then that’s another case for “profile hooks”–i.e., snippets to
run in the build process that produces the profile.

Thanks,
Ludo’.