[MacPorts] #30365: Additional option to selfupdate required if major changes take place

MacPorts noreply at macports.org
Mon Jul 25 12:49:44 PDT 2011


#30365: Additional option to selfupdate required if major changes take place
--------------------------------+-------------------------------------------
 Reporter:  bgschaid@…          |       Owner:  macports-tickets@…                   
     Type:  enhancement         |      Status:  new                                  
 Priority:  Normal              |   Milestone:                                       
Component:  base                |     Version:  2.0.0                                
 Keywords:                      |        Port:                                       
--------------------------------+-------------------------------------------
Changes (by ryandesign@…):

  * type:  request => enhancement


Comment:

 I don't think anything of the sort is necessary. MacPorts 2.0.0 isn't that
 different from MacPorts 1.9.x. One of our developers just decided we were
 going to call this release 2.0.0 instead of 1.10.0, and none of the other
 developers objected too much.

 There's no way we could have known back when we released MacPorts 1.9 that
 MacPorts 2.0.0 was going to store installed software differently on disk
 and that a conversion was going to be necessary. So there's no way we
 would have known to build an --upgrade-2.0 option into MacPorts at that
 time.

 Some selfupdates take longer than others. I don't think this is a problem.
 If the updates don't work for some reason, then that is a bug we need to
 fix.

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


More information about the macports-tickets mailing list