81aa6c721b
The go-build-system is slightly more appropriate, and switching resolves an issue with combining the 'unpack phase from the gnu-build-system, and the 'setup-go-environment from the go-build-system. With both of those phases creating a directory, the first-subdirectory call at the end of the 'unpack phase can return different values depending on the filesystem ordering. * gnu/packages/shellutils.scm (direnv)[source]: Use the git repository, as this works better with the go-build-system. [build-system]: Change to the go-build-system. [arguments]: Adjust for the go-build-system. [native-inputs]: Remove go. |
||
|---|---|---|
| .. | ||
| bootloader | ||
| build | ||
| installer | ||
| packages | ||
| services | ||
| system | ||
| tests | ||
| artwork.scm | ||
| bootloader.scm | ||
| ci.scm | ||
| installer.scm | ||
| local.mk | ||
| packages.scm | ||
| services.scm | ||
| system.scm | ||
| tests.scm | ||