OPAM release?
arthuraa opened this issue · 9 comments
Any plans to release this on OPAM? :)
That's a great idea @arthuraa. I've never used OPAM before, would you be able to help?
@jwiegley Yes, I could help. I could create an OPAM file for the project and submit a pull request to the archive. I'll do it as soon as I get some spare time.
@jwiegley @arthuraa before you submit any pull requests to the Coq opam archive, please resolve the license ambiguity for this project. The current README and the opam package file says "MIT", but the actual LICENSE file uses the BSD-3-Clause license text.
See for example here for the MIT license wording: https://spdx.org/licenses/MIT.html
@jwiegley unfortunately "BSD" is ambiguous. If you submit this to the archive, please use "BSD-3-Clause" instead (based on the current text in LICENSE
). The nitpicking is unfortunate but we hope to add automation to check licensing in the near future.
Sure thing. Pushed.
Thanks. If you want to put this project in the Coq opam archive, you now have two options (not mutually exclusive):
- put a Git-based opam package definition in the
extra-dev
repository - make a tag in the GitHub repo and put an opam package referencing a tarball for the tag in the
released
repository
Both of these are done by submitting a pull request to the archive. I can help if you want, but it might suffice to see an example: https://github.com/coq/opam-coq-archive/pull/1982/files