[MacPorts] #55385: ocaml: fails to build on 10.6 and lower
MacPorts
noreply at macports.org
Wed Nov 22 19:08:39 UTC 2017
#55385: ocaml: fails to build on 10.6 and lower
---------------------+----------------------
Reporter: mojca | Owner: pmetzger
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: ocaml |
---------------------+----------------------
Comment (by mojca):
I'm stealing this ticket for a while for other issues, but my suggestion
would be the following:
* In case it's possible to trivially fix this particular issue first, that
would be helpful because of the planned changes on 100+ other ports. (Btw:
where did you get the number 300? Did you also count the patchfiles?) That
is: if you move the other ports before fixing this, all those changes will
generate errors on the buildbot just because of the failure to build
dependencies and you would need to rebuild them later. But don't spend too
much time on it as dealing with old systems is not the highest priority,
it makes more sense to first make sure that ocaml works well on newer
systems. (If you could remove that flag by some conditional patching on <
10.6, fine, else don't bother.)
* You may go through some old tickets (some are 10 years old) where the
`port` field contains `ocaml` and figure out if any of them happen to be
addressed already, or if an upgrade to the latest version solves the
problem. If that requires small independent patches, you can submit them
separately, so that we apply them before the "big move". If ports are
obsolete, feel free to delete them. If some issues have been addressed,
ask on IRC if someone can close them for you (or collect such requests in
another ticket perhaps?)
* I would suggest to then try to move ports to a different subfolder and
add an additional category. And let the buildbots try to build all of
them. Just moving the ports should be sufficient to trigger a rebuild. You
may collect some basic statistics about which ports need an updated etc.
along the way.
* Then collect statistics about which ports failed, so that you can
address those later.
Just a few ideas.
--
Ticket URL: <https://trac.macports.org/ticket/55385#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list