[MacPorts] #40293: Avoid building broken/incompatible ports on buildbots (or don't report an error)

[MacPorts]

#40293: Avoid building broken/incompatible ports on buildbots (or don't report an
error)
-----------------------------+-------------------------
  Reporter:  mojca@…         |      Owner:  wsiegrist@…
      Type:  enhancement     |     Status:  new
  Priority:  Low             |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+-------------------------

Comment (by larryv@…):

 Replying to [comment:4 mojca@…]:
 > Yes, I had a separate keyword in mind, for example
 > {{{
 > buildbot.skip
 > }}}
 >
 > Maybe not a keyword for this exclusively, but there might be other
 > things which could be useful to assist the buildbot.

 I am very much against adding Portfile features that even acknowledge the
 existence of our Buildbot system, because it is completely accessory and
 not critical to MacPorts. I’m all for enhancing the system server-side,
 but not by adding cruft to Portfiles.

 And I don’t see the problem with allowing failing builds. What happens if
 Port A requires Port B, which is marked to be skipped without failing? I
 don’t even think base can handle this situation.

 > I'm not sure what that could be at the moment, but the first example
 > that comes to mind would be
 > {{{
 > buildbot.variant +quartz
 > buildbot.variant +x11
 > }}}
 > to request from the buildbot to build with both {{{+x11}}} and
 > {{{+quartz}}}. Before #35897 gets implemented, this could be used to
 > build {{{qt4-mac +universal}}} and other special cases that justify
 > the extra building time.

 Allowing port maintainers to dictate which binary archives get built does
 not seem like a good idea to me.

 > (Why has the other ticket been open for so long? Maybe now that
 > buildbots exist, this would be another reason to fix this.)

 Frankly, it’s never been fixed because it’s not really a problem. Just
 erroring out is kind of messy but more-or-less works. Enforcing platform
 versioning would really just be syntactic sugar for the way it works now.

-- 
Ticket URL: <https://trac.macports.org/ticket/40293#comment:8>
MacPorts <http://www.macports.org/>
Ports system for OS X