Fwd: Build Failure: (from, 10.6, OS, This, X, builds, configure.compiler=macports-gcc-4.7, newer, on, only, and 6 more

Clemens Lang cal at macports.org
Sun Dec 11 14:59:13 CET 2016


On Sun, Dec 11, 2016 at 03:38:14PM +0100, René J.V. Bertin wrote:
> > Because it runs 'port -q info --line --subports' and parses the
> > result. The flags to info guarantee that only the list of subports
> > is printed.
> 
> Portindex? I'm pretty sure I've had a ui_msg for a while in one of my
> PortGroups without ever running into side-effects. I kind of
> appreciate certain messages in the portindex output, in fact.

No, the buildbot scripts. The rule still stands: Don't print anything
from a Portfile outside of a phase.

> On Sunday December 11 2016 14:59:52 Mojca Miklavec wrote:
> 
> > There is no way to fix the buildbot scripts to work around that.
> 
> I doubt that, esp. not if you consider the possibility (and overall
> good idea) to extent `port info` to print information for machine
> reading.

'port info' output is already parsed by scripts today. It's output is
already machine-readable when using -q info --line --$fieldname. Your
change breaks this.

-- 
Clemens


More information about the macports-dev mailing list