But I'd like remind .warning directive pollutes stderr
Warnings are NOT pollution...
and discouraged portupgrade which was designed to catch messages from
stderr and rises errors.
I'd say, the portupgrade needs fixing, if it does, indeed, choke on
non-empty stderr without actual non-zero exit code. stderr is for
diagnostics, and is exactly the right place for warnings...
Now there are a few ports (ImageMagic and GhostScript*) where the
directive was appeared. I think the ports should be fixed to use
ECHO_MSG to display the warnings.
IMO, "ECHO_MSG" is hideous...
-mi
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
