ocaml-dune / ocaml-dune/binary-distribution
Where are the binaries? (asking for use in github actions)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 4
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Hello and thank you for this repo,
Continuing from a discussion from setup-dune here I'd like to understand a bit more the setup. For some reasons I was expecting to see either binaries artifacts in the dune project itself, or perhaps releases here but I could find neither.
So I wonder:
- Where are the raw binaries that this website is serving?
- What is the job that builds them and (presumably the same as) create the gh attestations?
The reason I ask is that I'd like to bypass the need for downloading the install.sh script altogether when installing a stable version of dune from github actions. I was thinking, if this is the case that there are some dune.exe raw binaries somewhere on GitHub infrastructure, using their internal network from there to gh-actions seems like a promising approach that I'd find worth exploring.
I'm thinking a sort of end goal where there exists a version of type Dune_stable_version.t -> string which is a template URL where I can download the dune binary (or a .tar.gz containing it) directly with e.g. curl.
Thank you for your help!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked setup-dune discussion and the install.sh script, then trace the repository's binary build and attestation jobs. Document where stable binaries are produced and determine whether a direct binary or archive URL can be exposed; done means the source and a supported download approach are clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100