Repository navigation
Use git to read .cabal files by name - #67
Conversation
This allows a bare checkout `all-cabal-hashes`, which saves some space and removes a lot of separate files. But it also means that we'll be able represent a whole `all-cabal-hashes` repo as a single git .pack-file. Making that .pack-file reproducible will be a final thing to achieve typeable#41.
|
BTW, bare checkout of |
| installPhase = '' | ||
| mkdir -p $out | ||
| git clone --branch hackage https://github.com/commercialhaskell/all-cabal-hashes.git $out | ||
| git clone --bare --branch hackage https://github.com/commercialhaskell/all-cabal-hashes.git $out |
There was a problem hiding this comment.
@binarin does --bare imply that the result of git clone is reproducible, and we can actually use fetchgit instead?
There was a problem hiding this comment.
No, now --bare just decreases the size of the derivation by removing uncompressed files / duplication.
It's needed because one way to make fetchgit reproducible is to generate a reproducible git {{.pack}}, and then create a full blown git repo from it. But this should be done without using git itself, as we don't know what else it'll decide to create. And bare repo is very easy to create from just a {{.pack}}-file and a commit hash using just a few bash commands.
There was a problem hiding this comment.
Ok, I see. Nice improvement nevertheless 👍
This allows a bare checkout of
all-cabal-hashes, which saves some space and removes a lot of separate files.But it also means that we'll be able represent a whole
all-cabal-hashesrepo as a single git .pack-file.Making that .pack-file reproducible will be a final thing to achieve #41.