[opam-devel] build bot monitoring the opam-repository

Fabrice Le Fessant Fabrice.Le_fessant at inria.fr
Wed Mar 23 11:06:02 GMT 2016

Hi Anil,

On Wed, Mar 23, 2016 at 11:53 AM Anil Madhavapeddy <anil at recoil.org> wrote:

> The build bot looks like it could also benefit from the container
> infrastructure, since that takes care of depexts for a number of
> distributions.

Currently, we use the same computer for all compilations (my personal
server at OVH), which means we have only one configuration of external
packages. It's both a good thing (we can re-use binaries from previous
compilations) but also a limitation (we cannot compile two packages that
would have conflicting external dependencies). Indeed, running the bot on a
large number of distributions would solve that later issue.

Before I look further at this, I just wanted to confirm that the licensing
> of the buildbot is intended to be fully AGPLv3.  It looks like there's a
> fork of opamLib here:
> https://github.com/OCamlPro/opam-builder/tree/master/libs/copam renamed
> under the copam namespace.

Yes, everything should be AGPLv3 with an attribution exception, except some
LGPL files that should have kept their original license. Copam itself is
not a copy of opamLib, but a wrapper around the opam command. There are
maybe a few files which were taken from OPAM (the Debian versioning, the
lexer and parser for OPAM files), they should be under LGPLv3. I will check
that the original headers for these files were kept, indeed.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/opam-devel/attachments/20160323/2d5faf24/attachment.html>

More information about the opam-devel mailing list