Hi,
I am missing any mention about the current etc/profile file inside of built Guix profiles. Is it planned to also change the function of the search paths in profiles? Because for example currently it can happen that GIO_EXTRA_MODULES will get set, because dconf is propagated into the profile, and this can break, even on Guix system, the expected so files used. The home profile packages can pick up the system so files and when the home profile hasn't been rebuilt yet, you get crashing programs. I think this means the env var needs to get effectively replaced instead, or not set at all by the profile's etc/profile file. This seems to be quite 'common' (after there start to be ABI incompatibilities, it's common for users to go asking in the irc channel about this) when libdconfsettings.so ends up in one of the search path folders. 1. After this change, are packages still going to respect the env var as well, or will the ones patched and having etc/search-path.d just ignore them completely? (replace v prepend) And if they won't ignore them, how is this incompatibility outlined higher going to be fixed, if anyhow? 1(b). What if user combines the profiles? For example, I will install python and python-numpy to system profile, then python and python-matplotlib to user profile. When I start python, which search path is actually used? Currently both are as the env var is just merged, but it doesn't seem to be possible to me with etc/search-paths.d (at least unless the various search-paths.d folders are going to be in an env var, but I think that would go against the motivation that env vars shouldn't be 'leaking'. Although they wouldn't be leaking to childs exactly, they would still be leaking from the profiles sourced.) 2. Is something going to happen to the search-paths / native-search-paths functionality of the package records in regards to guix profiles? (in other words will the generation of etc/profile file in guix profiles be afected) And if so, how exactly? I can't seem to comprehend it being removed completely as some build systems just won't have the patches, at least yet, on the other hand how would it be distinguished which ones should end up in the profile exports and which ones should just end up in the search-paths.d files? Apologies if I've just missed answers to these questions in the GCD text or discussion. Regards, Rutherther
