[MacPorts] #16085: port deactivates then activates active dependency if more than one "latest" version of a port is installed

[MacPorts]

#16085: port deactivates then activates active dependency if more than one "latest"
version of a port is installed
--------------------------------------+-------------------------------------
  Reporter:  ryandesign at macports.org  |       Owner:  macports-tickets at lists.macosforge.org
      Type:  defect                   |      Status:  new                                  
  Priority:  Normal                   |   Milestone:  MacPorts base bugs                   
 Component:  base                     |     Version:  1.7.0                                
Resolution:                           |    Keywords:                                       
--------------------------------------+-------------------------------------
Comment (by ryandesign at macports.org):

 Replying to [comment:2 ryandesign at macports.org]:
 > This leads to quandary !#2: if the active version is not the latest, and
 we do need to deactivate it and activate the latest version, what if
 there's more than one latest version installed (with different variants)?
 Which one do we activate? We may want to activate the one with the most
 similar variants to the currently-active one. Does the code currently do
 this? I don't know which one it picks. This may be a matter for another
 ticket, or it may in fact be too special a case to warrant spending a lot
 of time on, but I wanted to point it out.

 Here's what currently happens:

 {{{
 $ port installed lcms
 The following ports are currently installed:
   lcms @1.16_0
   lcms @1.16_0+universal (active)
   lcms @1.17_0
   lcms @1.17_0+universal
 $ port upgrade dcraw
 --->  Deactivating lcms @1.16_0+universal
 --->  Activating lcms @1.17_0+universal
 $
 }}}

 That's fine: 1.16_0+universal was active and MacPorts deactivated it and
 activated 1.17_0+universal.

 {{{
 $ port installed lcms
 The following ports are currently installed:
   lcms @1.16_0 (active)
   lcms @1.16_0+universal
   lcms @1.17_0
   lcms @1.17_0+universal
 $ port upgrade dcraw
 --->  Deactivating lcms @1.16_0
 --->  Activating lcms @1.17_0+universal
 $
 }}}

 Not fine: 1.16_0 (non-universal) was active but MacPorts still chose to
 activate 1.17_0+universal even though a non-universal 1.17 was available.

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