gbaz

> It should be manual with default false. I cannot change the default of the flag now that it is manual. Ah, that's frustrating. That doesn't correspond to the documentation,...

Search the api page for “revision” and you’ll see the data is available in json if the request specifies the content type. there’s some other revision resources in json there...

I don't think that we would want to extend hackage with hash-based downloads -- it already provides a number of mechanisms for retrieving packages and cabal revisions both, as detailed...

I'm not sure what you're getting at with pre-fetched metadata? Do you mean via use of cabal itself? I think a good approach could be just using the `sdistTarball` function...

when cabal generates a plan.json it will always use the latest metadata revision (unless it is explicitly passed timestamp telling it to do otherwise), which is also what `callHackageDirectly` will...

Hackage does build and run tests. This can be disabled per-package on hackage: https://hackage.haskell.org/package/copilot-bluespec/maintain This is however not an ideal situation, as it has to be done for each version....

Adding packages to the nix config for running tests as well as building haddocks should be fine, within reason, imho.

That's not the intention. Rather, the nix config for hackage-builder is to provide third party non-haskell binaries that are necessary for building (and testing as well) packages uploaded to hackage.

this looks good to me. @bgamari i think we'll need to deploy the builder and the main hackage in sync for this... when you get time, take a look and...

This is an interesting model! However, I don't think removing package associations from uploaders is a good practice. But skimming the docs its not so sure to me that this...