From owner-freebsd-ports@FreeBSD.ORG Tue Apr 10 15:18:09 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97AF2106566C; Tue, 10 Apr 2012 15:18:09 +0000 (UTC) (envelope-from rflynn@acsalaska.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 590498FC08; Tue, 10 Apr 2012 15:18:09 +0000 (UTC) Received: from [127.0.0.1] (squeeze.lan.rachie.is-a-geek.net [192.168.2.30]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id C86BF7E849; Tue, 10 Apr 2012 07:18:07 -0800 (AKDT) Message-ID: <4F844F19.8070005@acsalaska.net> Date: Tue, 10 Apr 2012 17:17:45 +0200 From: Mel Flynn User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: gahr@freebsd.org References: <201204092351.q39Npi6F025202@repoman.freebsd.org> <20120410091537.GK98668@gahrfit.gahr.ch> <20120410114537.GL17460@culot.org> <20120410115630.GB2456@lonesome.com> <20120410124449.GB73185@gahrfit.gahr.ch> <20120410144741.GC73185@gahrfit.gahr.ch> In-Reply-To: <20120410144741.GC73185@gahrfit.gahr.ch> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-clx-sbcl Makefile ports/palm/coldsync ... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 15:18:09 -0000 On 4/10/2012 16:47, Pietro Cerutti wrote: > On 2012-Apr-10, 11:20, Marcelo Araujo wrote: >> 2012/4/10 Pietro Cerutti >>> >>> >>> I might agree on that. But how is a DEPRECATED port better than a BROKEN >>> one in this regard? >>> >>> >> In my point of view, no make sense have a bunch of ports that actually >> doesn't works or because there is a fetch problem or even it is set as >> BROKEN. Who never was upset when need and find a port but it is BROKEN for >> some reason, In my view, have a port BROKEN or haven't it, is the same. Of >> course, I mean when a port is BROKEN for all plataforms as well as for all >> FreeBSD version. > > I agree on that. > >> >> I believe set it as DEPRECATED is a good way to make the maintainer take >> attention to fix it soon as possible, due he has put effort to insert this >> software on the ports tree in the past. > > What about submitting a PR, as we usually do for anything else? If it's > ok to wait 15 days (maintainer timeout) to commit an update to a port > that brings in important features, it is even more so to wait to > deprecate one. Not to discredit your work in any way, but 6 months of being BROKEN can be classified as maintainer timeout in the general case. Also given the error you're seeing it sounds like a very specific case that shouldn't affect the generally solid deprecation policy that is in effect - the bulk of the deprecation cases are upstream abandonware with an equally absent maintainer. I check the list of deprecated ports regularly when I feel nostalgic for , java-based rollover menus and "News" from the previous millennium. On a more constructive note - why don't you mention the specific port? Maybe some of us on the list can help you figure out why some files sometimes don't get byte compiled or provide you with a work-around solution (dynamically generated plist comes to mind). -- Mel