[MacPorts] #59381: Do something better when no ports are specified

[MacPorts]

#59381: Do something better when no ports are specified
--------------------------+--------------------
  Reporter:  6aKa         |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------

Comment (by ryandesign):

 There's also some difficulty with tracing a particular build directory
 back to the port that created it. The user may have multiple ports trees;
 a build directory could be from any of them. Suppose a user has a build
 directory from the port zlib from the main ports tree, and then makes a
 local port repository and copies the zlib port there, modifies it, and
 builds it. Now the user has a second build directory for that copy of
 zlib. So even though we could write new code to scan the build directory
 and translate those build directory names back to port names, in this case
 we would find that there are two build directories for zlib, but telling
 MacPorts to clean zlib would only clean one of them (whichever one came
 first in sources.conf).

 So that may doom the "failed" or "dirty" pseudoport idea. A better way to
 accomplish the task of cleaning up failed builds is through reclaim; see
 #60126. This improvement to reclaim will be in a future version of
 MacPorts.

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