#40293: Avoid building broken/incompatible ports on buildbots (or don't report an error) -----------------------------+--------------------- Reporter: mojca@… | Owner: admin@… Type: enhancement | Status: new Priority: Low | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Changes (by mojca@…): * owner: wsiegrist@… => admin@… Old description:
There are certain ports which are known to be broken ({{{hugin-app}}} chokes when including {{{boost}}} headers for example - one could add a keyword to the port to let the buildbot know that) or which are known to be incompatible with a certain version of Mac OS X (wxWidgets 2.8 won't compile on 10.7 and later).
Would it be possible to avoid building these ports on the buildbot (or at least avoid treating that failure as an error)?
New description: There are certain ports which are known to be broken or which are known to be incompatible with a certain version of Mac OS X (wxWidgets 2.8 won't compile on 10.7 and later). And there are ports like `p5-graveyard` and `py-graveyard` whose compilation on the buildbot might take more than a day and are programmed in such a way that they don't produce any package/output at all. The whole process is just a hack to allow auto-upgrade (and all the subports in the graveyard port are programmed to fail). Would it be possible to skip building some of these ports on the buildbot (or at least avoid treating that failure as an error)? -- -- Ticket URL: <https://trac.macports.org/ticket/40293#comment:13> MacPorts <https://www.macports.org/> Ports system for OS X