<civodul>let's hope you don't receive all the support requests ;-)
<zimoun>yeah, I hope that «community is small» is understood as «long queue for support» ;-)
<zimoun>it is impressive how Conda is popular… and broken for reproducing in the same time.
<zimoun>Ok, now let focus on the next tutorial in Grenoble :-)
<rekado>I don’t mean to be mean by introducing this analogy, but Conda’s popularity is not too different from how pathogens colonize a sanitized surface.
<rekado>for many people Conda was a *huge* step up over the barren software toolshed they found themselves in
<rekado>for some it was “pip install” this and ask the sysadmin to install some other library globally
<rekado>Conda was one of the first tools to be vastly superior to the terribly inconvenient state of software installation tools for scientists
<rekado>ecological succession is a slow process, and sometimes hindered by the success of early colonizers
<rekado>ironically it is often the incredible success of early colonizers that becomes their liability
<rekado>(incidentally, *this* is how I like to use the term “ecosystem”, not as a poor synonym for “market economy”)
<zimoun>«Therefore, the worse-is-better software first will gain acceptance, second will condition its users to expect less, and third will be improved to a point that is almost the right thing.» https://dreamsongs.com/WIB.html
<zimoun>I agree about «*huge* step up over the barren». That’s why I initially used Conda. And it does well this job.
<zimoun>I often miss from questions in audience this point: Conda does X for reproducibility. When Conda is broken by design for reproducing. It is in their manual, section Solver. Ah, a classical RTFM. ;-)
<zimoun>rekado: this morning, I had questions about GWL. Yeah!
<civodul>(incidentally, i wasn't aware of the 8K module limit, that's... interesting)
<PurpleSym>I had a version, which kept references to the packages in Guix proper. But in an effort to reduce the number of exports I removed them. Would have been nice to not break existing manifests when moving, but it happens all the time anyway, so -.-
<PurpleSym>rekado: Unfortunately this split between guix-cran and Guix proper sometimes causes version conflicts, with packages in guix-cran requiring newer versions of packages in Guix proper.
<rekado>civodul: re microservices: yes, the system container is a bit heavy for what I want to accomplish
<rekado>I punted on network interface handling; generated the container launcher with “--network” (this should really be an option for the run-container launcher, not for “guix system container” which generates the launcher), set LD_LIBRARY_PATH for sssd in multiple locations, shared the host system’s /var/lib/sss/pipes, fiddled with pam… and it works
<rekado>we now have a multi-user RStudio on our server, running in a reproducible container, talking to the host system’s sssd.
<rekado>it does agree, though, that ‘GNU/Linux’ would be more accurate than ‘Linux’.
<rekado>‘the name "GNU/Linux" more accurately reflects the fact that the operating system is a combination of the Linux kernel and the GNU userland, and recognizes the important role played by the GNU Project in its development and evolution.’
<rekado>it keeps regurgitating ‘Guix, Guix, <corny platitude>’ in poems and lyrics. It’s great.