[MacPorts] #28469: VirtualBox-OSE 4.0.10

[MacPorts]

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

Comment(by carsomyr@…):

 Replying to [comment:24 rmstonecipher@…]:
 > Replying to [comment:23 carsomyr@…]:
 > > Replying to [comment:22 rmstonecipher@…]:
 > > > SNIP
 > > > P.S. - many library dependencies appear to be included in this
 source.[[br]]
 > > > Are all of these fixed-version dependencies required, or can
 VirtualBox use dynamic libraries?
 > >
 > > What fixed version dependencies do you speak of?  Do you mean fixed
 versions like libxml-2.0?
 > >
 > > I've folded in your ./configure patch and updated the port archive
 with the changes (see virtualbox-port-4.0.10.tgz).  Consequently, I have
 some questions of my own:
 > >  1. I've been told in an earlier part of this thread that md5 is
 obsolete as a checksum.  Should it be included?
 > >  2. Should post-deactivate hooks attempt to unload the port?  "port
 unload" doesn't seem to be invoked when VirtualBox is uninstalled.  This
 is kind of disturbing, since kernel modules are involved.
 >
 >  1. If you will allow others to periodically upgrade the port as new
 versions are released, it is easiest to just edit the version and paste
 the output of 'port -d checksum' which, as of now, includes md5.
 >  2. Regarding unloading during uninstall, I think that's a great idea.
 [http://trac.macports.org/browser/trunk/dports/audio/mpd MPD] has a
 similar problem which leads to headaches during upgrades.  So far for MPD
 my best solution has been to reboot after upgrading - a rather inelegant
 solution to what should be a simple operation.  This may be worth bringing
 up on the [https://trac.macports.org/wiki/MailingLists macports-dev]
 mailing list.[[br]]
 > Cheers,[[br]]
 > Ryan Stonecipher

 Ok, I am taking from the answers above that no further actions should be
 taken and a solution would result in a change to the MacPorts base.  Is
 ticket #14774 related, by any chance?  I was thinking that:
  1. Unload on port deactivation always happens.
  2. Reactivation happens only during an upgrade and when the previous
 version was deactivated from the "loaded" state.

 Let me know if you encounter any new issues with the revised port.
 Looking forward to its inclusion!

 -Roy

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