Janneke Nieuwenhuizen wrote: > Are are we creating a problem for > bootstrapping (or even a dependency cycle) when introducing this new > dependency into a certain package.
I think you answered this question with "no", when writing in [1]: "Even more recently (2018), the GNU C Library glibc-2.28 adds Python as a build requirement" So, how do you avoid Python when building glibc? Do you use musl libc as a first stage, and only build glibc once a python built with musl exists? Also, from the diagrams in [1][2][3] it looks like the full-source bootstrap uses tarballs frozen in time (make-3.80, gcc-2.95.3, gcc 4.7.3, etc.). So, even if newer versions of 'make' or 'gcc' will use a Python-based gnulib-tool, there won't be a problem, because the bootstrap of these old tarballs will be unaffected. Bruno [1] https://guix.gnu.org/en/blog/2023/the-full-source-bootstrap-building-from-source-all-the-way-down/ [2] https://guix.gnu.org/manual/en/html_node/Reduced-Binary-Seed-Bootstrap.html [3] https://guix.gnu.org/manual/devel/en/html_node/Full_002dSource-Bootstrap.html
