.warning directives in Makefile

[Mikhail Teterin]

On п'ятниця 27 червень 2008, Sergey Matveychuk wrote:
= 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.

Some criteria! FreeBSD is not a common way to keep computers running either...

= Why do you think portupgrade needs fixing?

I already said, why -- there is nothing wrong with using stderr to warn. All 
compilers do that, for one example -- that's /exactly/ what stderr is for: 
diagnostic information. Try redirecting cc's stdout to /dev/null -- you'll 
still see the warnings (unless you also redirect stderr).

If foo chokes on that, you should be contacting foo's maintainer, but that's 
not me (nor do I maintain imagemagic or ghostscript, BTW). In case of 
portupgrade, the foo is not even part of FreeBSD -- I don't understand, why 
you think, you can demand patches from me...

Yours,

	-mi