3.5 KiB
Notes
sdists
Do we need to make sdists? I think so.
Does cabal sdist need cabal.project?
Perhaps using Distribution.Simple directly?
Idk, I don't understand sdists.
sources
supporting only tarballs now
- url: https://...
anything curl can handle will work here
- url: file://...
Different versions of the same package can co-exist. The tool will check for name and version collisions.
Note: perhaps include hash validation? this can be done later
revisions?
Files in a special folder
revisions/bar-0.2.0.0.cabal
automatically become revisions for, e.g., package bar version 0.2.0.0
It can be done with hackage-repo-tool update
run_ "hackage-repo-tool" ["update", "--keys", toTextIgnore (_keys config), "--repo", "repo.tmp/", "--verbose"]
Obtaining a package name and version by filename is ok, see 9a5f2d16fc/hackage-repo-tool/src/Main.hs (L575-L586)
Note: one could rewrite 9a5f2d16fc/hackage-repo-tool/src/Main.hs (L196) and do it in one go
patches
I am not sure whether I want to support patches or not. Basically one could simply fork and point the repo to the new source. On the otherside, hackage-overlay-repo-tool is made especially for patches so there might be a real need for it. For the time being,I am not supporting patches.
output
No more than a directory full of files.
- Can be served over HTTPS
- Served on ipfs
- Committed to git
- Can be tar'gzipped and moved
- All of the above
- nix-compatible hash of the whole thing
usage
many ways to use this.
quick and easy
served through https (nginx, s3, GitHub)
repository packages.example.org
url: https://packages.example.org/
secure: True
Note: we don't even need GitHub Pages. A raw.githubusercontent.com is good enough for cabal.
totally reproducible
repository packages.example.org
url: https://packages.example.org/HASH
secure: True
properly secure
repository packages.example.org
url: https://packages.example.org/
secure: True
root-keys: <root-key-IDs>
key-threshold: <key-threshold>
with root-keys available from webpage
locally available
useful for nix
repository my-local-repo
url: file:/path/to/local/repo
secure: True
website
It might be nice to have a minimal website generated along the repository
Things to include:
- list of packages, with their metadata and link to cabal files
- hashes of everything, ready to cut and paste
- instructions, snipped to add to cabal.project or cabal.config
- previous deployments/versions
I would much prefer if there was a way to keep the website separate from the output above (for hash friendliness). The presentation layer can be separate. Perhaps something that can fetch the data and render on the spot? Something with Cloudflare Pages and Workers?
Maybe just a separate directory with a bunch of links, deployed on a separate branch on GitHub
Branches:
- main (the source of all evil)
- repository (the assembled repository)
- website (the rendered website, with links to the repository branch)