George Clemmer <myg...@gmail.com> writes: > Mark H Weaver <m...@netris.org> writes: > >> On my GuixSD system where substitutes are completely disabled and I >> build everything locally, I've been running my Guix daemon with both >> --gc-keep-derivations=yes and --gc-keep-outputs=yes for years. Here's >> the relevant excerpt of my OS config: > ... > > Thanks. Very cool to see. IIUC there is a Guix "bootstrap" component. > Using this config, where does that come from?
The bootstrap binaries currently consist of statically-linked executables for 'bash', 'tar', 'xz', and 'mkdir', which are included in the Guix source tree in the gnu/packages/bootstrap/ directory: https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/bootstrap and also a few additional tarballs of statically-linked binaries downloaded from: https://alpha.gnu.org/gnu/guix/bootstrap/ which includes guile, gcc, binutils, glibc, and a "static-binaries" tarball with coreutils, tar, gzip, bzip2, xz, patch, sed, grep, and gawk. These bootstrap binaries were generated by the code in gnu/packages/make-bootstrap.scm in the past, and are rarely changed. They are fetched/imported into the store by code in gnu/packages/bootstrap.scm. The current bootstrap binaries for x86_64-linux and i686-linux were generated in November 2013, although there is ongoing work to replace these with a reduced set of bootstrap binaries: https://alpha.gnu.org/gnu/guix/bootstrap/i686-linux/20181020/ It is likely that our 'master' branch will be based on these reduced bootstrap tarballs, or similar ones, within a few months. Mark
