[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] upper bounding of mirage packages in mainline opam-repo



On 12/06/2016 10:12 AM, Anil Madhavapeddy wrote:

Dear all,

The mainline OPAM repository needs to have an upper bound on Mirage2 related 
packages to make room for the incoming 3.0 releases (that are currently staged 
in https://github.com/mirage/mirage-dev).

Thanks to a fancy new CLI-based upper-bounding tool from Mindy Preston, and 
more importantly, the tool's application to opam-repository, these 3 PRs have 
now been merged:

https://github.com/ocaml/opam-repository/pull/7975
https://github.com/ocaml/opam-repository/pull/7974
https://github.com/ocaml/opam-repository/pull/7973

Please let us know if you spot any unexpected package regressions due to this.

If anyone wishes to help Mindy to generalise the CLI upperbound-constrainer, 
the source is here:
https://github.com/yomimono/upperbound-constrainer

upperbound-constrainer is a pretty dumb wrapper around `opam-file-format`, so thanks are really owed to Louis Gesbert. (Note that it needs unreleased functionality in opam-file-format, so you'll need to pin that package in order to use it.)

A lot of the pain involved in setting upper bounds on old packages comes from having `opam lint` run for the first time on `opam` files that haven't been looked at in years. A useful piece of automation would be something nicer than https://github.com/yomimono/opam-lint-remover , which can only resolve errors 25, 35, and 36 given fields that are populated in later versions.

-Mindy

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.