Hello! Janneke Nieuwenhuizen <[email protected]> skribis:
>> And, there’s some good news! I hear fellow hackers have been working on >> this thing called BLUE, which could address our tarball problem as well! >> That is, once Guix uses BLUE as its build system, ‘make dist’ is >> effectively gone, > > Well, "someone" actually contributed some patches to BLUE *), making sure > that `make dist' would produce a reproducible source tarball ootb ;) > > Possibly BLUE should support a `make git-dist' or something; but as a > generic build system you'd probably not want have a hard dependency on > git? Dunno... [...] > *) https://codeberg.org/lapislazuli/blue/pulls/251 > https://codeberg.org/lapislazuli/blue/pulls/258 Nice! I’m looking at ‘tarball.scm’ and it’s not entirely clear what ‘inputs’ contains: can it be more than just the list of source files (checked in)? I would expect no? Put differently, when would one ask BLUE to create a tarball instead of using ‘git archive’? Thanks, Ludo’, slowly sliding off-topic. :-)
