From owner-freebsd-ports@FreeBSD.ORG Thu Dec 19 13:04:46 2013 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 252F5A4 for ; Thu, 19 Dec 2013 13:04:46 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EF0641EB7 for ; Thu, 19 Dec 2013 13:04:45 +0000 (UTC) Received: from [192.168.1.2] (ip70-178-7-237.ks.ks.cox.net [70.178.7.237]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id EF42F435A3; Thu, 19 Dec 2013 07:04:27 -0600 (CST) Message-ID: <52B2EECA.10908@marino.st> Date: Thu, 19 Dec 2013 14:04:10 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Erich Dollansky Subject: Re: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing References: <52B0D149.5020308@marino.st> <20131219135421.63d7cd20@X220.alogt.com> In-Reply-To: <20131219135421.63d7cd20@X220.alogt.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: David Demelier , "ports@FreeBSD.org" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2013 13:04:46 -0000 On 12/19/2013 06:54, Erich Dollansky wrote: > you got the point. We have to assume that a port which is not marked > broken has to work. I build the entire port tree several times a month. I can tell you from experience that this assumption is not valid. > So, the fault is on our side. Why should we spam > GNATS with our problem? > GNATS for confirmed problems, the list for anything else. Where is this cited? PRs are not for confirmed problems. They are for any problem. However, this kind of "confirmation" post is not the type of post I was complaining about. Unless your "confirmation" is no more than an except of a log, then it is. To iterate my opinion, if a breakage is a symptom of a systematic issue, or the port in question breaks like 6000 dependent ports, the ports@ is appropriate. If it's a single broken port, then a PR is appropriate. Alternatively, email the maintainer only. The majority of us on this list do not care about individual broken ports and getting a sent a log is noise at best. John