Ricardo Wurmus <rek...@elephly.net> writes: > 宋文武 <iyzs...@gmail.com> writes: > >>>> We can set 'GTK_EXE_PREFIX' to the '~/.guix-profile', and generate the >>>> 'immodules.cache' files in a profile hook. It will work for both gtk2 >>>> and gtk3 applications. > >>> Does this mean that GTK needs to be installed in the user’s profile for >>> this to work? I thought ‘GTK_EXE_PREFIX’ would change the path of >>> ‘$libdir’ for *all* of GTK’s libraries. It can only have one value, not >>> a list of paths to look for libraries. > >> Yes, this require install GTK+ into user's profile. >> Also, there is a 'GTK_DATA_PREFIX' in a same situation, which I think is >> the only way to set the GTK+ 2 theme. > > Isn’t this a little too high a price to pay? One can only install one > (major) version of GTK+ into a profile, so when we begin propagating the > GTK inputs users will run into conflicts. > > I would really like to avoid propagating GTK+ (although it may be a bad > idea to have software depend on different minor versions of GTK+). It > would be very nice if only additional modules—such as explicitly > installed themes and input method modules—would have to be installed to > the profile. Those who do not need themes or input methods would not > need to be bothered with this at all.
I guess the question is: what would be the uglier fix? Do we prefer to force users to have GTK+ installed in their profiles, or are we okay with patching the GTK+ sources such that additional environment variables would be respected, allowing users to specify different module directories for version 2 and version 3? ~~ Ricardo
