Mikhail Teterin wrote:
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
Well, only imagemagic and ghostscript* use .warning. It is NOT a common
way to print warnings.
Why do you think portupgrade needs fixing?
--
Dixi.
Sem.
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
