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 19:27:55 CET 2016


On Sun, Dec 11, 2016 at 08:14:13PM +0100, René J.V. Bertin wrote:
> > > Just as machine readable as this line. 
> >
> > Wrong, since 'port -q info --line --$fieldname' by definition only
> > contains information on $fieldname, whereas your message contains
> > natural language.
> 
> Clutching at straws much? :)
> 
> Regardless, your argument insinuates something that is true only for a
> subset of the values $fieldname can take on. 

But this subset is exactly the set of values that you'd parse in a
script, whereas you'd usually not parse the ones that contain natural
languge (why would you to split long_description at commata?).

> > That would happen if you were using ui_warn or ui_error.
> 
> So those are not incompatible with the build script?

No, but it would still be wrong to use them to print a message while a
port is opened. Multiple places in MacPorts assume that Portfiles do not
print messages while execution, e.g. dependency calculation,
rev-upgrade, etc.

-- 
Clemens


More information about the macports-dev mailing list