<mark_weaver>it can be skimmed without harm. they are essentially tests.
<lfam>mark_weaver: I didn't realize it was okay to skip that phase. But I just checked and there are some packages that do it.
<mark_weaver>skipping that phase is analogous to skipping the 'check' phase. the only harm is that some problems might go unnoticed.
<lfam>I'm reading the comments in the places where we skip it. Interesting reading
<balduin>@mark_weaver: thanks. I think it would be a good idea to be able to add paths. Especially because in my case library is in `/gnu/store/hash-package-name/`, but the runpath-validate paths only include `/gnu/store/hash-package-name/subdir`
<mark_weaver>balduin: you mean a .so library is directly in /gnu/store/hash-package-name/ ?
<mark_weaver>if so, that's a problem. something is going wrong in the package build system, or you're using it wrong.
<mark_weaver>that would be analogous to a more traditional "make install" putting libraries or executables directly in /usr
<balduin>no sorry, it is in `/gnu/store/hash-package-name/lib`, but looks only in `/gnu/store/hash-package-name/lib/subdir`
<mark_weaver>balduin: what makes you think validate-runpath is not looking in /gnu/store/.../lib ? that's where most libraries in guix are installed, and afaict validate-runpath looks there.
<detrout>what does the % mean in that (assoc-ref %outputs...)?
<mark_weaver>detrout: in scheme, '%' can appear in identifiers, and it has no special meaning to the language itself.
<detrout>mark_weaver: but it seems to have meaning in guix build scripts?
<detrout>in a lambda with (#:key outputs) I can refer to the output variable
<detrout>but outside of the lambda... it doesn't seem to, unless maybe with the %?
<mark_weaver>I guess civodul started those identifiers with '%' to call attention to them, I guess because they are made available to the scheme code snippets in package definitions without being explicitly bound in a way the user can see.
<mark_weaver>detrout: they are defined in the 'prologue' at the top of build-side scheme scripts, which ultimately contain all of the snippets of code created from package descriptions and build systems. see where 'prologue' is defined in guix/derivations.scm line 1195
<yang>So would anyone be interested to write me the basic command lines onto pastebin for setting up the network and sshd ? So I can ssh into the box and test it further ? The VNC renders really slowly for me