From owner-freebsd-ports@FreeBSD.ORG  Fri Jun 27 11:45:24 2008
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E8E67106568A;
	Fri, 27 Jun 2008 11:45:24 +0000 (UTC)
	(envelope-from mi+kde@aldan.algebra.com)
Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224])
	by mx1.freebsd.org (Postfix) with ESMTP id 9FA548FC1B;
	Fri, 27 Jun 2008 11:45:24 +0000 (UTC)
	(envelope-from mi+kde@aldan.algebra.com)
Received: from aldan.algebra.com (localhost [127.0.0.1])
	by aldan.algebra.com (8.14.2/8.14.1) with ESMTP id m5RBHbM7011095
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 27 Jun 2008 07:17:38 -0400 (EDT)
	(envelope-from mi+kde@aldan.algebra.com)
Received: from localhost (localhost [[UNIX: localhost]])
	by aldan.algebra.com (8.14.2/8.14.1/Submit) id m5RBHb28011094;
	Fri, 27 Jun 2008 07:17:37 -0400 (EDT)
	(envelope-from mi+kde@aldan.algebra.com)
From: Mikhail Teterin <mi+kde@aldan.algebra.com>
To: Sergey Matveychuk <sem@freebsd.org>
Date: Fri, 27 Jun 2008 07:17:36 -0400
User-Agent: KMail/1.9.9
References: <4863C0D2.1020804@FreeBSD.org> <4863C80E.2010309@aldan.algebra.com>
	<486496A7.1000402@FreeBSD.org>
In-Reply-To: <486496A7.1000402@FreeBSD.org>
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVihy+z3/UR{6SCQ
MIME-Version: 1.0
Content-Type: text/plain;
  charset="koi8-u"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200806270717.37326@aldan>
Cc: freebsd-ports@freebsd.org
Subject: Re: .warning directives in Makefile
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2008 11:45:25 -0000

On =D0'=D1=D4=CE=C9=C3=D1 27 =DE=C5=D2=D7=C5=CE=D8 2008, Sergey Matveychuk =
wrote:
=3D Mikhail Teterin wrote:
=3D >=20
=3D >> But I'd like remind .warning directive pollutes stderr
=3D > Warnings are NOT pollution...
=3D >> and discouraged portupgrade which was designed to catch messages fro=
m=20
=3D >> stderr and rises errors.
=3D > I'd say, the portupgrade needs fixing, if it does, indeed, choke on=20
=3D=20
=3D Well, only imagemagic and ghostscript* use .warning. It is NOT a common=
=20
=3D way to print warnings.

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

=3D Why do you think portupgrade needs fixing?

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

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

Yours,

	-mi