<rekado_>I want to use guix to manage different versions of bioinformatics software on our cluster. I very much appreciate the way guix liberates users, so that they are no longer at the mercy of sysadmins to install software.
<rekado_>still, as a sysadmin I wonder if there are admin features that would allow me to install software into users' profiles and restrict them from installing software that hasn't yet been built.
<rekado_>I think I'll need to demonstrate that we have some form of control over what work the daemon performs to have a chance of having my proposal accepted.
<rekado_>I also wonder if users can just make the daemon build packages from local user-provided modules.
<rekado_>will guix pick up any module file that's on a user's load path? Or is only the daemon's load path important?
<rekado_>(I'm afraid of users convincing the daemon to download and execute stuff from the Internet.)
<tadni>civodul: I just noticed... does the center of the Guix logo, supposed to look like a lambda?!
<tadni>I didn't notice till I started playing around with the *.svg
<Tsutsukakushi>an option to make menuconfig style dialog to choose the options when installing from sources, this would mak the .scm more complicated but would enable more people to install a package with customized options
<rekado_>civodul: will the daemon *do* whatever users ask it to? Does it do *everything* it is asked to do in a chroot and as the unprivileged build users?
<civodul>a malicious user could cause DoS by filling up the store
<civodul>but in a cluster setup, that's not a realistic threat IMO
<rekado_>I'm wondering: users don't actually need to have access to the guix executable, right? They only need to have a profile. Can an administrator install software specifically for a particular user profile?
<rekado_>I see that there is --profile for guix package.
<civodul>the administrator could populate user profiles, yes
<civodul>but IMO it's better for users to be able to run 'guix' by themselves
<civodul>that will allow them to choose what to install, whether/when to upgrade, etc.
<rekado_>for desktop systems I agree, but I'd have a hard time convincing the cluster admins of permitting our use of guix. It seems that admins only reluctantly give up part of their superuser powers...
<civodul>rekado_: in the cluster we have at work, admins take care of providing 'modules'
<civodul>but users are often unhappy with the available modules, upgrade policy, etc.
<civodul>another argument, is that 'guix' simply allows users to build packages
<civodul>which they can already do manually anyway
<Sleep_Walker>X11/extension/Xcomposite.h is present and maybe even found, but it includes X11/extension/composite.h
<rekado_>we often have users who attempt to compile software on their own, but having to mess around with the environment variables is a struggle, so in the end it's the admins who have to package up software centrally.