[Bug 234878] emulators/virtualbox-ose: Update to 6.1

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234878

--- Comment #92 from Mikhail Teterin <mi at FreeBSD.org> ---
(In reply to Mario Lobo from comment #89)
> we are lagging so far behind on the hosting side (ose and ose-kmod) that I think people that are trying to upgrade it aren't even thinking about the guest-additions port.

We are, obviously, lagging on _both_ sides -- and the "not thinking" is mutual.
Most people interested in -- and capable of -- upgrading one side, aren't using
the other, and must rely on others for testing their changes. This leads to
delays...

Delays so high, people lose interest, and Oracle manages to make several
releases in between -- obsoleting the original work. That the work is happening
in little GitHub repos is not helping either :(

This ticket is old, and has 90+ comments and lots of attachments -- our problem
is not lack of interest or expertise, it is organizational.

I'd like to expand my proposal (from comment #88) with this plan:

1. Leave the current virtualbox-* ports be (or upgrade them to the latest 5.x).
2. Repo-copy each virtualbox-foo to the ...foo6.
3. Disconnect the new virtualbox-ose-additions6 (guest) from the new
virtualbox-ose6 (host) by:
   a) giving the guest its own files/ (for patches) and distinfo;
   b) moving the guest-only patches from the host's files/ into the guest's;
   c) enumerate the few -- if any -- patches necessary to both sides as
EXTRAPATCHES in the guest -- or even just copy them over.
4. Assign the sides to different maintainers.

If no one objects to these steps in principle -- and no one volunteers to do it
-- I'll perform the copying/moving myself. I can also take up maintainership of
the new virtualbox-ose-additions6, if there is no better candidate (my own
usage is limited to a FreeBSD-11.x/i386 PAE guest inside a Windows 10 desktop).

Based on one of the many attachments here, I can also upgrade the new hosting
virtualbox-ose6 port (once), but I will not be able to test it beyond "it
compiles".

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.