In reply to @emilytrau:matrix.org
but am i missing something or could you fetchurl a release tarball and use ungz and untar from mescc-tools-extra?

I tried pulling the whole repo but it was upset by the symlinks.
I'm guessing after gnutar and gnuzip we can do that but we need a couple files for those exact packages 😅

also pulling the whole of live-bootstrap is quite a big source where we'll only use a handful of files hopefully. IDK if the priority will be less bytes pulled in or less total separate derivations.
One nice thing about the separate files is it's very clear exactly which subset of files from live-bootstrap are inherited

I made some other ux changes to get a trimmed subset of files so you can do

lbf = live-bootstrap-files.getSubsetOfFiles "sysa/${pname}-${version}/";
# ...
cp ${lbf."mk/main.mk"} Makefile
cp ${lbf."files/stat_override.c"} some/place/file.c

It grabs live-bootstrap but then deletes most files

https://github.com/schierlm/FullSourceBootstrapFromGit/blob/main/part01.sh#L27-L28

specifically in this folder we see it uses config.h & mescc.scm which we just make ourselves so that's covered

pushed a copy. I noticed some of the files for coreutils come from a different commit so having some capability for multiple target commits would be good

https://github.com/06kellyjac/nixpkgs/commit/a106f98d9fb82a5640413289dd9c7f2dd7f5b6db

I might permanently move the files source of truth to nix & only fetch hashes for items that are empty e.g. "somefile.txt" = ""; and maybe look to parallelise it although I don't think we want to pull many many files that'd make that worth it

In reply to @emilytrau:matrix.org
John Ericson: something is up with the pname/version that gets exposed. any theories? https://search.nixos.org/packages?channel=unstable&from=0&size=50&sort=relevance&type=packages&query=minimal-bootstrap

In reply to @emilytrau:matrix.org
https://github.com/NixOS/nixpkgs/pull/232320

In reply to @emilytrau:matrix.org
https://github.com/NixOS/nixpkgs/pull/232320