<civodul>which means i need to increase the bandwidth with people who're not interested in Guix and just want to get things done "the module way" :-)
<civodul>so i've generated and avertised a bunch of modules on the local cluster here
<civodul>if one of you wants to give it a try, that'd be most welcome!
<zimoun>civodul: you are saying that ’module’ is incremental and ’guix shell’ not. That’s somehow wrong, “guix shell foo” then “guix shell bar” then ^D “guix shell baz” etc. provides the same incremental experience, IMHO.
<zimoun>Somehow, there is no reason for using module except futile resistance. ;-)
<civodul>same for PKG_CONFIG_PATH, C_INCLUDE_PATH, etc.
<zimoun>Somehow, I do not understand. On one hand, we are saying that it is how search paths works and on the other hand it is a counter example.
<civodul>what i'm saying is that "guix shell" computes search paths for the profile it's building
<civodul>it does not attempt to combine it with the "surrounding profile", so to speak
<civodul>by combining, i mean something like "guix package -p P1 -p P2 --search-paths"
<zimoun>yes and from my understanding it is the point of #37790; a way to “combine” profile depending on “surrounding profile”. Well, maybe something is lacking here. But now I took the habits with the current behavior that it is in my muscle memory. :-)
<zimoun>why each time I need a package from the Broad Institute, it is a spaghetti plate… arf!