[MacPorts] #28469: VirtualBox 4.0.4

[MacPorts]

#28469: VirtualBox 4.0.4
--------------------------------+-------------------------------------------
 Reporter:  carsomyr@…          |       Owner:  macports-tickets@…                   
     Type:  submission          |      Status:  new                                  
 Priority:  Normal              |   Milestone:                                       
Component:  ports               |     Version:  1.9.2                                
 Keywords:                      |        Port:  VirtualBox                           
--------------------------------+-------------------------------------------

Comment(by carsomyr@…):

 Ok, I've attached the revised port archive.  I made the following changes:
   * The category is now "emulators".  Although VirtualBox isn't exactly
 emulation, I found that BSD FreshPorts had the same classification.
   * openmaintainer -> nomaintainer.
   * The license keyword is GPL-2.
   * openssl and libsdl now use pkgconfig, thus enabling libsdl-devel to
 provide the lib dependency.
   * The "universal" variant has been disabled.
   * Added "supported_archs i386 x86_64".
   * Kernel extensions are now not loaded on VirtualBox activation.
 Instead, the following message is printed:
  {{{
 ################################################################################
 # A Mac OS X Startup Item for loading and unloading VirtualBox kernel
 # extensions has been generated at ${startup_items_dir}/VirtualBox; it
 will be
 # run at next boot or by typing:
 #
 # sudo SystemStarter start VirtualBox
 ################################################################################
  }}}
     Note that kernel extensions will be loaded on reboot, though.

 As for the Startup Items issue, I left it the way it was, for the
 following reasons:
   * The Startup Item was provided, with all metadata plists, by
 Sun/Oracle.
   * The act of loading kernel extensions is not a daemon.  The launchd
 daemon was designed to launch other daemons.  As such, it doesn't have any
 concept of a stop hook.  I believe that MacPorts' daemondo mechanism is
 meant for daemons, too.
   * Startup Items aren't deprecated; they're use for launching on-demand
 daemons is deprecated.  See this link for the Mac OS X boot process:
 http://bit.ly/hrfcdV+.  The documentation actually suggests using Startup
 Items for non-launch-on-demand daemons.  I would argue that Startup Items
 are better tied to the boot up / shutdown cycle for Mac OS, and that
 VirtualBox's kernel extension loading behavior is best implemented as
 such.
 Still, if it's absolutely necessary, I can convert the Mac OS Startup Item
 to a MacPorts "startupitem".  I just don't think it's appropriate given
 the uniqueness of the Port (unless there are other Ports out there with
 kernel modules that I'm not aware of).

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