On Oct 25, 2017, at 20:09, Craig Treleaven wrote: > If we’re going to do this, can we be a little more precise about “failed” > builds? > > 1) Any port that relies on a non-default variant “fails” on the buildbots. > All of my myth* ports will ALWAYS show a “failed” status on ALL of the > buildbots for this reason. I would rather that users were told that the > build was “not attempted”. Telling them that build “failed" isn’t helpful. > > 2) Any port that needs C++11 “fails” on the existing 10.7 and earlier > buildbots. > > 3) Various ports have a pre-fetch block that checks the OS version and > “fails” if it is not supported.
As I've said many times before, this is a big project, involving changes to MacPorts base to provide a mechanism whereby ports can indicate that a build is expected to fail in certain circumstances. I don't think any work has begun on defining or implementing that mechanism.
