Hi! Maxim Cournoyer <maxim.courno...@gmail.com> skribis:
> So given there's no technical reasons not to use libgit2, I'd use that > and keep the closure size down. For the record, that’s a 6% increase: --8<---------------cut here---------------start------------->8--- $ guix size guix | tail -1 total: 633.0 MiB $ guix size guix git-minimal | tail -1 total: 675.7 MiB --8<---------------cut here---------------end--------------->8--- (Of course it all adds up; I’m not saying we can dismiss it.) In the context of <https://issues.guix.gnu.org/65866> plus the lack of GC in libgit2 discussed in <https://issues.guix.gnu.org/65720>, my inclination is to include that hard dependency on Git. That’s not a happy choice for me, but it has the advantage of solving two immediate problems. I would revisit it as soon as libgit2 supports shallow clones (which is coming, as you write) and GC (or a workaround to that effect). SHA256 may also soon be a requirement: we’ll need to be able to clone repos that use it. How does that sound? Ludo’.
