From owner-svn-ports-all@FreeBSD.ORG Wed Sep 10 11:37:26 2014 Return-Path: Delivered-To: svn-ports-all@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 DEDE928B; Wed, 10 Sep 2014 11:37:26 +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 AF329308; Wed, 10 Sep 2014 11:37:26 +0000 (UTC) Received: from [10.31.9.236] (unknown [213.225.137.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 056E943BC5; Wed, 10 Sep 2014 06:37:07 -0500 (CDT) Message-ID: <541037D8.2010601@marino.st> Date: Wed, 10 Sep 2014 13:36:56 +0200 From: John Marino Reply-To: marino@freebsd.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: =?UTF-8?B?QmVybmhhcmQgRnLDtmhsaWNo?= , John Marino Subject: Re: svn commit: r367769 - in head: . emulators emulators/virtualbox-ose-kmod-legacy emulators/virtualbox-ose-legacy References: <201409091918.s89JIStw037486@svn.freebsd.org> <540F6D8A.30907@marino.st> <540F704B.7070209@FreeBSD.org> <540F716D.8020001@marino.st> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Bryan Drewery , ports-committers@freebsd.org X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 11:37:27 -0000 On 9/10/2014 12:36, Bernhard Fröhlich wrote: > I am quite sure nobody would use the kmod port on it's own - > nevertheless I would expect someone to mark ports as deprecated/expired > and/or reset maintainer like we have done so for ages. Is this really > the way we want to handle that? emulators/virtualbox-ose-legacy has been marked deprecated for months, automatically as a result of NO_STAGE being defined. On 1 September, it was marked BROKEN, automatically as a result of NO_STAGE being defined. Since 1 September, it has been unbuildable. So there is no question about virtualbox-ose-legacy. Regarding emulators/virtualbox-ose-kmod-legacy, yes, I could have marked it deprecated instead, but at least that as a minimum because otherwise it can fall in the cracks. I saw the two ports were created together, I came to the conclusion they came as a pair, and thus concluded they needed to leave as a pair. > Deleting the port means we will not build any packages for the next week > and many users will be surprised at least. I am currently on holidays so > I won't be able to fix it in the next couple of days. As I said, you wouldn't have had packages anyway. It has been BROKEN since 1 September. The net change is zero. > Yes, I am aware that the staging deadline has passes and I have staged > all my ports already but still this one port seems to have gone > unnoticed - for whatever reason. I will do my work to get it fixed but > it will take a few days. No user seemed to notice that it was deprecated or broken judging by the lack of a PR or mention on ports@ ML. Maybe the legacy version isn't going to be missed? John