From owner-freebsd-ports@FreeBSD.ORG  Fri Jun 27 07:30:03 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 E6C1C1065677;
	Fri, 27 Jun 2008 07:30:03 +0000 (UTC) (envelope-from sem@FreeBSD.org)
Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75])
	by mx1.freebsd.org (Postfix) with ESMTP id AAE948FC27;
	Fri, 27 Jun 2008 07:30:03 +0000 (UTC) (envelope-from sem@FreeBSD.org)
Received: from [77.41.76.79] (helo=[172.16.100.4])
	by mail.ciam.ru with esmtpa (Exim 4.x)
	id 1KC8PD-0001D1-Te; Fri, 27 Jun 2008 11:30:03 +0400
Message-ID: <486496A7.1000402@FreeBSD.org>
Date: Fri, 27 Jun 2008 11:28:39 +0400
From: Sergey Matveychuk <sem@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Mikhail Teterin <mi+mill@aldan.algebra.com>
References: <4863C0D2.1020804@FreeBSD.org> <4863C80E.2010309@aldan.algebra.com>
In-Reply-To: <4863C80E.2010309@aldan.algebra.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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 07:30:04 -0000

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.