Date: Wed, 10 Sep 2014 13:36:56 +0200 From: John Marino <freebsd.contact@marino.st> To: =?UTF-8?B?QmVybmhhcmQgRnLDtmhsaWNo?= <decke@bluelife.at>, John Marino <marino@freebsd.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Bryan Drewery <bdrewery@freebsd.org>, ports-committers@freebsd.org Subject: Re: svn commit: r367769 - in head: . emulators emulators/virtualbox-ose-kmod-legacy emulators/virtualbox-ose-legacy Message-ID: <541037D8.2010601@marino.st> In-Reply-To: <CAE-m3X3JQeTPU_01vYT39yaBfB8uefmcGYG9O5Fgy8zy3Dw3PQ@mail.gmail.com> References: <201409091918.s89JIStw037486@svn.freebsd.org> <CAE-m3X0VobD6WDC94QtgDFhFrQ_dYuZ=mMO4iPTUy7k3juUgeQ@mail.gmail.com> <540F6D8A.30907@marino.st> <540F704B.7070209@FreeBSD.org> <540F716D.8020001@marino.st> <CAE-m3X3JQeTPU_01vYT39yaBfB8uefmcGYG9O5Fgy8zy3Dw3PQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?541037D8.2010601>