[MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.

[MacPorts]

#47755: Broken symlink left by select code when selected port is deactivated causes
poppler and other ports using aclocal to fail during configuration.
-----------------------+--------------------------------
  Reporter:  lukasz@…  |      Owner:  macports-tickets@…
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  base      |    Version:  2.3.3
Resolution:            |   Keywords:
      Port:            |
-----------------------+--------------------------------

Comment (by keybounce@…):

 Replying to [comment:12 ryandesign@…]:
 > At this point we consider it a user error to deactivate or uninstall a
 port that you have selected with "port select". Perhaps MacPorts base
 should be modified to prevent you from deactivating or uninstalling a port
 that you've selected.

 Shouldn't "deactivating a selected port" coincide with "select 'none' as a
 followup"?

 I.e.: If I have python32 selected as my python, and I deactivate python32,
 should that make "none" the current python? (If I understand the issue
 correctly, this is what triggers it, right?)

 Equally, if I install python33, and there is no python selected, shouldn't
 python33 select itself as the python?

 So, if I have python32 installed and selected, and upgrade to 33, 32
 should deactivate, triggering "none", then 33 activates, and selects.

 Would this approach solve both this issue and the semi-obvious related one
 of "I installed 33, but now things break with no active python"?

-- 
Ticket URL: <https://trac.macports.org/ticket/47755#comment:38>
MacPorts <https://www.macports.org/>
Ports system for macOS