[MacPorts] #28469: VirtualBox 4.0.4

MacPorts noreply at macports.org
Thu Jun 30 02:10:30 PDT 2011


#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@…):

 Replying to [comment:22 rmstonecipher@…]:
 > Replying to [comment:21 carsomyr@…]:
 > > Replying to [comment:20 rmstonecipher@…]:
 > > > Roy,[[br]]
 > > > I attempted building your Portfile and noticed that it is not
 UsingTheRightCompiler.[[br]]
 > > > I'll make an effort to troubleshoot this (minor) issue and upload a
 patch for your Portfile.[[br]][[br]]
 > > > Cheers,[[br]]
 > > > Ryan Stonecipher
 > >
 > > Thanks!
 > >
 > > In the meantime, I've update the port archive to 4.0.10.
 > Roy,[[br]]
 > Attached is an updated 4.0.10 Portfile including this improvement.[[br]]
 > Can I test this port using existing disk images for machines created
 with the non-OSE VirtualBox?[[br]]

 Yes, I think so -- one version should be able to take over all of the
 internal data structures left by the other version.  If you want to be
 absolutely sure, you can "export appliance" and then "import appliance".

 > I would prefer to test before committing a port which requires a >65MB
 source download.[[br]][[br]]
 > Cheers,[[br]]
 > Ryan Stonecipher[[br]][[br]]
 > 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.

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


More information about the macports-tickets mailing list