[opam-devel] Github Releases, with excellent timing

Anil Madhavapeddy anil at recoil.org
Mon Jul 8 14:29:52 BST 2013

On 7 Jul 2013, at 17:04, Daniel Bünzli <daniel.buenzli at erratique.ch> wrote:

> Le mercredi, 3 juillet 2013 à 15:27, Anil Madhavapeddy a écrit :
>> None of these seem like substantive blockers. A quick online hunt shows that they're planning to extend the API to add Releases when it's stable. An API would let us easily automate including the CHANGES file in the release tag, as well as auto-generating the release tarballs with the autogen files. For now, I've experimentally released ocaml-cow to see what it looks like:
> Sure but at that point you actually implemented the damn thing by yourself, which does indicates that they released a toy…

To reiterate: it now has the facility for binary downloads, which they yanked about 12 months ago due to scaling issues.  You couldn't do that before, and you can do so now (albeit manually).

> In fact I realize now that opam's .install files do actually work as advertised. I don't think external tools or the github Release API are needed here (and we want to be able to consult that while being disconnected).
> With install files it's easy to add README{,.md} and CHANGES{,.md} to the doc directory of the package located in .opam/$SWITCH/doc/$PKG
> So it would just be a matter of looking up if these files exist in that directory and spit them out, or simply provide some kind of standard invocation to enable easy access to documentation directory of a package.

Yep, I agree with this.  Do you write your META files by hand at the moment?


More information about the opam-devel mailing list