package opam-publish
Install
Dune Dependency
Authors
Maintainers
Sources
md5=2d8fcf689db536d555a47686ada07c30
sha512=8214f1ec88b545b9aed93d6baf1dce6295372eaf6421b17fac7579e1318bd02ad5a4fc5e4754fb6ff92821deb433d8925265a184e5d0f841314bfce625ce3f62
README.md.html
opam-publish
A tool to ease contributions to opam repositories.
opam-publish
takes package definition files of your projects, and submits them to opam package repositories (ocaml/opam-repository by default).
Prerequisites
This version is for opam 2.0.0, and should not be used with repositories in older formats. A Github account is required.
Usage
Basic case, assuming your project is on Github
The same works for initial publications, new releases, and updates.
The following should be run from the source directory of your project
Make sure you have an
opam
file, orNAME.opam
files at the root of your projectCreate a tag:
git tag -a TAG; git push origin TAG
Run
opam publish
. This will install the tool if required.
You will be guided through the rest (creating a Github token the first time, reviewing the patch, etc.)
Additional possibilities
If your project is not on Github, you can specify the archive URL on the command-line.
If the opam files are not in the archive, or outdated, you can specify them on the command-line, or specify a directory where to look for them (e.g. opam publish URL .
).
Submitting to other repositories is possible, as long as they are on Github. See the --repo
option.
Updating already published packages is also allowed (as long as they don't use a files/
subdirectory)..
See opam publish --help
for more options.