From owner-freebsd-ports@FreeBSD.ORG Tue Apr 8 17:21:56 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3EC80A9B for ; Tue, 8 Apr 2014 17:21:56 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1774D1A44 for ; Tue, 8 Apr 2014 17:21:55 +0000 (UTC) Received: from [192.168.0.20] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 8FC0B43BB3; Tue, 8 Apr 2014 12:21:40 -0500 (CDT) Message-ID: <53443012.6070404@marino.st> Date: Tue, 08 Apr 2014 19:21:22 +0200 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Dave Duchscher , ports@freebsd.org Subject: Re: Suggestion for port maintainers References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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: Tue, 08 Apr 2014 17:21:56 -0000 On 4/8/2014 16:30, Dave Duchscher wrote: > Port Maintainers, > > Just a suggestion: If you are going to remove an option from your > port, it would be nice if you would make the port break when that > option is used. We build our own packages with custom options and > this little issue just caused some issues for us. We can’t watch > updates to every port we build and we just got bit by the option > APACHE being removed from lang/php5 port. However, it is totally within your control have a script monitor every port that you build for changes in options. You could even run it as a poudriere hook. There are hundreds of maintainers; you aren't going to reach all of them even if they all *all* agree with this suggestion. (I don't think I do. How long do I have to keep this non-option broken? 1 month? 1 year? forever? too much trouble.) John