svn commit: r367769 - in head: . emulators emulators/virtualbox-ose-kmod-legacy emulators/virtualbox-ose-legacy

[Bernhard Fröhlich]

Am 09.09.2014 23:30 schrieb "John Marino" <freebsd.contact at marino.st>:
>
> On 9/9/2014 23:25, Bryan Drewery wrote:
> > virtualbox-ose-kmod-legacy does not have a dependency on unstaged
> > emulators/virtualbox-ose-legacy. Naturally decke@ was not notified.
>
> Okay, so the issue is the kmod port?
> I didn't realize it had a function by itself, I thought it existed
> solely for virtualbox-ose-legacy.
>
>
> > It is not proper to remove a port without a deprecation period if it
> > works and has no other reason to be removed.
> >
> > btw decke@ still is a portmgr.
>
>
> The language is inexcusable.

Yes it is. Sorry did not want to get rude.

> If virtualbox-ose-kmod-legacy is useful by itself, I'm happy to restore
it.

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?

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.

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.