[MacPorts] #31180: emulators/virtualbox-oracle-vm-virtualbox-extension-pack

[MacPorts]

#31180: emulators/virtualbox-oracle-vm-virtualbox-extension-pack
----------------------------------+-----------------------------------------
 Reporter:  pixilla@…             |       Owner:  macports-tickets@…                   
     Type:  submission            |      Status:  new                                  
 Priority:  Normal                |   Milestone:                                       
Component:  ports                 |     Version:  2.0.3                                
 Keywords:                        |        Port:                                       
----------------------------------+-----------------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@…, royliu@… (added)


Comment:

 Replying to [ticket:31180 pixilla@…]:
 >  1. The license is listed as (PUEL). Would MP have an issue with this
 license? [http://www.virtualbox.org/wiki/VirtualBox_PUEL VirtualBox_PUEL]

 Item 7 of their [https://www.virtualbox.org/wiki/Licensing_FAQ licensing
 FAQ] says "The Personal Use and Evaluation License [...] does not give you
 the right to redistribute these binaries" so we'd have to notify Bill to
 add an exception to the mirroring rules for this port (as we already do
 for the molden port). And we wouldn't be able to distribute archives, but
 setting "`license PUEL`", since PUEL isn't in our list of approved
 licenses, should take care of that already. Since "Personal Use and
 Evaluation License" is a bit generic, I might use "VirtualBoxPUEL" as the
 license name.

 >  2. The port name "virtualbox-oracle-vm-virtualbox-extension-pack" is
 rather long. I originally used "virtualbox-extpack" for the name then
 wondered if some day there were many extensions would this still be a good
 name. Any opinions regarding the name?

 This is a long name, and slightly redundant. It doesn't particularly
 matter to me. But we could use a shorter name like "virtualbox-extension-
 pack" for now, and if later this becomes ambiguous, we can always change
 it (`replaced_by ...`).

 Since the version of this extension pack should probably stay in sync with
 the virtualbox port, maybe it would make sense to make it a subport of the
 virtualbox port. See #32615 in which I showed how I would do this for
 virtualbox-guest-additions.

-- 
Ticket URL: <https://trac.macports.org/ticket/31180#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS