<DusXMT>rekado-: The idea is that it only gets loaded into memory once, so if you have eg. 5 Qt programs running at a time, they share the same in-memory copy of the libraries. Of course, I _do_ agree with you :)
<efraim>if we package the libraries and load them as propogated inputs, will they be used instead of bundled Qt libraries?
<DusXMT>efraim: indeed, but I think you mean as normal inputs, as propagated inputs are usually used for tools and the like
<davexunit>yeah, for the software that guix has knowledge of i.e. not your ubuntu stuff, it can tell you some nice things such as what environment variables you should configure to make things work since we don't use /usr
<nextos>davexunit: ok, i really like dependencies are not insane like in nix
<nextos>with nix i installed mutt, and python2 eventually came in too
<davexunit>in the future I think we'll have a better story for running the daemon as an unprivileged user.
<davexunit>it *can* run unprivileged, but there's no isolation and things break.
<davexunit>user namespaces can address this, but require a more recent kernel.
<rekado_>csed: thanks. I'm currently (with too many interruptions) working on letting users manage their profiles on their own on all cluster nodes. This is currently the biggest practical limitation of having a central (mostly-)read-only store.
<csed>rekado_: Not sure how well our users would manage that. Only two labs here are bioinformaticians.
<rekado_>I don't know how comfortable our users will be with this change.
<rekado_>it shouldn't be too hard for them to learn a few common commands.
<rekado_>for others there's still the low-bandwidth way of asking me for help :)
<nextos2>davexunit: shouldn't be git broken down to avoid getting subversion and python2 as defaults?
<rekado_>I also think that our git package is a little fat.
<alezost>ACTION is for git-minimal (and mpv-minimal)