Hi Mathieu! [email protected] skribis:
> commit 37861f6c293d7ed1033050b2b0597885ba65186f > Author: Mathieu Othacehe <[email protected]> > AuthorDate: Fri Jul 9 12:07:24 2021 +0200 > > ci: Add bootstrap packages to the core subset. > > * gnu/ci.scm (%bootstrap-packages): New variable. > (cuirass-jobs): Add it to the core subset. [...] > +(define %bootstrap-packages > + ;; Return the list of bootstrap packages from the commencement module. > + (filter package? > + (module-map > + (lambda (sym var) > + (variable-ref var)) > + (resolve-module '(gnu packages commencement))))) > + > (define (packages-to-cross-build target) > "Return the list of packages to cross-build for TARGET." > ;; Don't cross-build the bootstrap tarballs for MinGW. > @@ -508,7 +517,7 @@ valid." > (map (lambda (package) > (package-job store (job-name package) > package system)) > - %core-packages) > + (append %bootstrap-packages %core-packages)) I believe the effect is that the same-named packages, those not in commencement.scm, are no longer being built, as discussed here: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00222.html Should we arrange so that jobs for the commencement.scm packages get a custom name, for example prefixed by “commencement.”? Thanks, Ludo’.
