[ocaml-platform] Is it taking too long for OCaml software to become 4.03-compatible? Would release process changes help?
yminsky at gmail.com
Thu Jun 30 12:40:23 BST 2016
Including ppx-rewriters in the distribution would be the wrong resolution,
I think. The modularity afforded by the current world is worth a lot,
letting independent sets of people to work on different pieces of the
infrastructure, and making the work of the core team as simple as possible.
I think the core team should be loathe to give this up.
Having some kind of compatibility story that most PPXs could use which
would make PPXs compatible across compiler versions could help a great
deal, though. Maybe that's where the effort can be best spent. Such a thing
could even be done outside of the core distribution, though it would have
to be among the very first packages ported. Indeed, given that it would
need to work with multiple compiler versions, it is perhaps best for it to
be developed outside.
On Thu, Jun 30, 2016 at 4:57 AM Fabrice Le Fessant <
Fabrice.Le_fessant at inria.fr> wrote:
> If you look at the announce of opam-builder, you will notice that it was
> monitoring 4.03.0+beta1 from the beginning:
> 4.03.0+beta2 was monitored too, as soon as it was released.
> But indeed, opam-builder's website is far from perfection, it could be
> faster to load, send notifications by email, recognize and display error
> messages (and much more, as the information sleeping there is huge...). We
> will try to improve it when we have time, but for now, it is on our
> spare-time list of projects.
> I agree with Yaron that PPX are more and more going to become a problem
> for upgrading to the latest OCaml, as Camlp4 was before (and is still,
> unfortunately). Many packages now depend on ppx-rewriters, that will almost
> never be in sync with trunk, which makes testing trunk very hard, even if
> we patch OPAM not to use the upper-bounds on ocaml-version in package
> descriptions. Soon, OCaml users will probably ask us to merge some
> ppx-rewriters in the OCaml distribution to force the sync, as they asked
> for Camlp4 long ago.
> On Thu, Jun 30, 2016 at 9:19 AM Alain Frisch <alain.frisch at lexifi.com>
>> On 30/06/2016 03:56, Alain Frisch wrote:
>> > OCamlPro's opam builder (
>> > http://opam.ocamlpro.com/builder/html/report-last.html ) really needs
>> > be more advertised and its UI a bit polished to encourage people to
>> > actually look at it. Also a report per maintainer (with emails sent
>> > automatically?) could be useful.
>> Here is some wishlist for this tool:
>> - Add trunk testing: this is what will put pressure for people to
>> continuously upgrade their packages. Ideally, it would also show the
>> (date of the) latest successful build on trunk. Same for release
>> branches once they are forked.
>> - Make the grid more narrow to fit more versions on a screen (e.g.
>> abbreviate Broken Deps to "Deps") and show more recent versions
>> (including trunk) to the left.
>> - By default, show only the latest version of each package.
>> - Add a mode where packages are grouped by maintainer.
>> - Try to make the errors more visible. E.g. for
>> the section "=== ERROR while compiling github.1.0.0 ==" could be moved
>> to the top of the screen.
>> - There could also be heuristics to detect the error and show
>> directly in the main report grid the category. For instance,
>> is simply about a new warning and "-warn-error A" in the package.
>> - It would be useful to force building package even if they claim they
>> are not compatible with the latest version (or trunk). For instance, I
>> was curious about why ocamlnet.4.0.4 did not build with 4.03. (In case
>> people wonder, the first problem comes from the new error on multiple
>> definitions of exceptions with the same name; this error was introduced
>> on trunk in 2014 IIRC. The fix for ocamlnet is just to remove one line.)
>> Platform mailing list
>> Platform at lists.ocaml.org
> Platform mailing list
> Platform at lists.ocaml.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Platform