<lfam>I don't think this would be an issue in the installer image, but sometimes people use `su` improperly on Guix and get the wrong PATH. The default root PATH when using `su` is '/sbin:/bin:/usr/sbin:/usr/bin', and none of those paths exist for Guix. This is documented in the su(1) man page. One must use `su --login` to get the Guix-y PATH
<troydm>lfam: one question how do I install new software like I want to install some tools, I just change config.scm and run reconfigure again? I'm pretty much new to this configuration oriented system thing
<troydm>lfam: also if I consequently run reconfigure without changing config on second run ideally their shouldn't be any compilation/downloading actions at all right?
<lfam>troydm: Generally, I recommend reading the manual section 'GNU Distribution', speficially the subsection 'System Configuration'. But, on GuixSD, you can have "global packages" that all users see, and those come from config.scm, like you suggested. But users can also do their own package management in the normal Guix way.
<lfam>Building the system based on config.scm (that is, `guix system build` or `guix system reconfigure`) takes into account both config.scm and the version of Guix used by whoever is doing the reconfigure. That's usually root. So if you do `guix pull && system system reconfigure ...`, there will probably be new packages to download or build even though you haven't edited config.scm
<lfam>You might think of `guix pull` as being similar to `apt-get update`
<rekado>I had a great time at the easybuild user meeting.
<rekado>Kenneth Hoste made this a very relaxed environment in which to discuss ideas.
<rekado>the reception of my talk was very good and we ended up talking about our experiences with packaging scientific software, and we exchanged ideas about our outlook on the viability of packaging software in the future.
<lfam>That does sound good, I'd be interested to hear more of the discussion