Hi, Marius <[email protected]> writes:
> Good evening, Maxim > > > I would like to see that diagram that you talked about in the last message > (somehow the attachment did not get attached, or i did not recieve it on my > end). Sorry, I included it from a an opened buffer in Gnus, and apparently something went wrong. Here it is again. The work is not mine, it was fetched from the intertubes some time ago.
> > So basically we have this workarounds in /etc/profile because in the case you > install perl on system guix profile and xmlperlparser on your user guix > profile, then some environment variables are not setup correctly, right? > The current /etc/profile does not specifically fixup the Perl search paths, but you got the idea right. > All roots to the fact that merging paths in /etc/profile works, but in > ~/.bashrc (with guix --search-paths) does not? I think you mean ~/.bash_profile instead of ~/.bashrc? Environment variables should be defined once for the whole session, not in ~/.bashrc, generally. The current eval is in the ~/.bash_profile skeleton. It looks like it should cover for the manual merging done in /etc/profile, albeit that's part of a recent (2 years old) skeleton that is only copied for new system installations/user creation, so some users may not have it, while /etc/profile is guaranteed to be created as defined in the Guix sources. Note that we now have a etc-bashrc-d-service-type, perhaps that could be used preferably to skeletons, as we can update/fix bugs in these and they get pushed to Guix System users upon reconfiguring their system. > How is that? Because i'm comparing my merged paths in /etc/profile and in > .bashrch and they give the same merged paths. The only difference is that > .bashrc when calling guix package --search-paths adds additional env vars. > > > My question is, is this workaround fixed in the current guix version (for > what i've seen) but kept in /etc/profiles just to provide a backwards > compatibility for when guix package --search-path did not exist? It looks like based on my feedback then we wanted a NEWS entry, which they was added in a later reply to the thread but not reviewed yet. > I feel like this problem has already been patched with the addition of the > home profile definition that merges paths. But it only lasts to remove the > old workaround from /etc/profile, right? > > In conclusion, are we dealing with a case were the fix was applied but > the old workaround wasn't removed? I mean, users were even told by > news that /etc/profile may not merge paths anymore. But the code still > remains there. If that's the case, then what's left is to remove the > old workaround from /etc/profile The four patches in bug#20255 should be applied, tested and reviewed, and then we can close this bug I think. If something extra can be cleaned up from /etc/profile, all the best. Would you like to try doing so? -- Thanks, Maxim
