[ocaml-infra] [opam-devel] Automatically synching GitHub pulls to OPAM

Amir Chaudhry amc79 at cam.ac.uk
Fri Feb 7 16:46:38 GMT 2014

Does seem very useful and an easy way for package maintainers to see how proposed patches might affect them..

Naiive question (since I haven't tried this myself): Does the switch grab the latest trunk version and apply the patch or does it take 4.01.0 and apply it?  I notice that the PRs are all for trunk.

I guess what I'm curious about is whether different people will end up with different things depending on when they do the switch.  i.e if trunk has advanced in the meantime.

Best wishes,

On 7 Feb 2014, at 16:37, Thomas Gazagnaire <thomas.gazagnaire at gmail.com> wrote:

> That's awesome!!!
>> I can publish this regularly as a custom remote, but it occurs to me that during the 6-month GitHub experiment, we may as well merge this directly into OPAM stable.  Most users will not see all the extra repositories due to requiring the --all script.
> I think that's a great idea, but would be nice to automatically remove closed PRs though if we do this.
> Also, not sure how to handle the PR which adds / modifies the configure options, but we could fix that later.
> --
> Thomas
> _______________________________________________
> Infrastructure mailing list
> Infrastructure at lists.ocaml.org
> http://lists.ocaml.org/listinfo/infrastructure

More information about the Infrastructure mailing list