Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-04-07 | doc: Fix typos from codespell lint | Yerzhan Mazhkenov | |
2021-04-05 | guix: Add troubleshooting documentation entries | Carl Dong | |
2021-04-01 | guix: Use --cores instead of --max-jobs | Carl Dong | |
In Guix, there are two flags for controlling parallelism: Note: When I say "derivation," think "package" --cores=n - controls the number of CPU cores to build each derivation. This is the value passed to `make`'s `--jobs=` flag. - defaults to 0: as many cores as is available --max-jobs=n - controls how many derivations can be built in parallel - defaults to 1 Therefore, if set --max-jobs=$MAX_JOBS and don't set --cores, Guix could theoretically spin up $MAX_JOBS * $(nproc) number of threads, and that's no good. So we could either default to --cores=1, --max-jobs=$MAX_JOBS - Pro: --cores=1 means that `make` will be invoked with `-j1`, avoiding problems with package whose build systems and test suites break when running multi-threaded. - Con: There will be times when only 1 or 2 derivations can be built at a time, because the rest of the dependency graph all depend on those 1 or 2 derivations. During these times, the machine will be severely under-utilized. or --cores=$MAX_JOBS, --max-jobs=1 - Pro: We don't encounter prolonged periods of severe under-utilization mentioned above. - Con: Many packages' build systems and test suites break when running multi-threaded. or --cores=1, --max-jobs=1 and let the user override with $ADDITIONAL_GUIX_COMMON_FLAGS | |||
2021-03-01 | guix, doc: Update default HOSTS value | Hennadii Stepanov | |
2021-02-22 | guix: Passthrough SDK_PATH into container | Carl Dong | |
2021-02-19 | guix: Update conservative space requirements | Carl Dong | |
2021-02-16 | guix: Passthrough BASE_CACHE into container | Carl Dong | |
This allows depends-built packages to be cached. | |||
2021-02-12 | doc: Guix is shipped in Debian and Ubuntu | MarcoFalke | |
2021-01-21 | guix: README: Add darwin HOSTS entry | Carl Dong | |
2021-01-08 | guix: Small updates to README wording | Carl Dong | |
2021-01-08 | guix: Update HOSTS README entry for new architectures | Carl Dong | |
2021-01-08 | guix: Remove README development environment section | Carl Dong | |
2021-01-08 | guix: Add ADDITIONAL_GUIX_{COMMON,TIMEMACHINE}_FLAGS options | Carl Dong | |
2021-01-08 | guix: Add SUBSTITUTE_URLS option | Carl Dong | |
2020-05-20 | guix: Add clarifying documentation for V env var | Carl Dong | |
2020-05-01 | guix: Remove logical cores requirement | Carl Dong | |
Thanks MarcoFalke for pushing this to its limits and testing :-) | |||
2020-04-02 | guix: Remove dead links from README. | Carl Dong | |
2020-02-09 | build: Skip i686 build by default in guix and gitian | MarcoFalke | |
2020-01-27 | guix: Update documentation for time-machine | Carl Dong | |
Wait a minute, doc. Are you telling me you built a time machine... Out of a functional package manager? | |||
2019-07-12 | contrib: guix: Additional clarifications re: substitutes | Carl Dong | |
2019-07-12 | contrib: guix: Various improvements. | Carl Dong | |
- Clearer and more accurate prose - Pin `guix pull' to commit rather than branch - Just use `use-module' instead of `define-module' - Use `bash-minimal' instead of `bash' - Remove unneeded `tcsh' from manifest - Explicitly use `python-3.7' - Add comments about how {native,cross}-toolchains are produced and why | |||
2019-07-12 | contrib: guix: Clarify SOURCE_DATE_EPOCH. | Carl Dong | |
2019-07-12 | contrib: Add deterministic Guix builds. | Carl Dong | |