[MacPorts] #49752: root5: runs "port select root ..." on behalf of user, causing unregistered files to be left on the user's system

MacPorts noreply at macports.org
Wed May 2 16:13:59 UTC 2018


#49752: root5: runs "port select root ..." on behalf of user, causing unregistered
files to be left on the user's system
-------------------------+--------------------------
  Reporter:  ryandesign  |      Owner:  cjones051073
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.4
Resolution:              |   Keywords:
      Port:  root5       |
-------------------------+--------------------------

Comment (by cjones051073):

 The point is from my perspective, the most convenient for users is to
 leave the root ports as is, so have them run port select. Personally I
 don't think from the user point of view the situation currently in place
 is really any different to what happens if a user installs root(5,6), runs
 port select themselves, then later on uninstalls root and root_select
 forgetting that they previously ran port select and that they need to undo
 this first. Files are left behind not associated to any installed port
 just the same. This is not something special to the root ports, but any
 port using the select mechanism. I don't really agree that the fact the
 root ports do this for the user, makes the situation really any different.
 Its still a flaw in the port select mechanism.

 However, the issue for me, and why I would consider removing the automatic
 setting, is whether this is causing issues on the buildbots, leaving files
 behind. How much of an issue that is I cannot judge, as I am not familiar
 with the details on running the buildbots...

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


More information about the macports-tickets mailing list