Federico Beffa <be...@ieee.org> skribis: > Adding 'dconf' and 'libcanberra' as default inputs to > 'glib-or-gtk-build-system' would make many of these problems go away, > with the only drawback of a possibly unused entry in an environment > variable.
Another drawback is that it will increase the size of the closure of each package that is concerned (‘emacs’ is at 835 MiB without dconf nor libcanberra.) > However, if you want to be super accurate then yes, this > will not do. I guess it’s a trade-off. How difficult would it be to identify applications that require the dconf GIO module (Totem, Evince) vs. those that can live without it (Emacs)? Likewise, what fraction of the ‘glib-or-gtk-build-system’ packages require dconf? Based on that, we could choose to either make it opt-in (that is, explicitly add dconf as an input when needed), or opt-out (dconf is an implicit input of ‘glib-or-gtk-build-system’ that can be removed with #:dconf? #f). Similarly with libcanberra. How does that sound? Ludo’.
