Re: [MacPorts] #43085: MacPorts port should not be installable (was: MacPorts 2.3 »beta« already released via selfupdate ?)

[MacPorts]

#43085: MacPorts port should not be installable
------------------------------+--------------------------------
  Reporter:  stephan.jorek@…  |      Owner:  macports-tickets@…
      Type:  defect           |     Status:  closed
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.2.1
Resolution:  fixed            |   Keywords:
      Port:  MacPorts         |
------------------------------+--------------------------------
Changes (by cal@…):

 * status:  new => closed
 * resolution:   => fixed
 * port:   => MacPorts


Comment:

 Replying to [comment:2 stephan.jorek@…]:
 > Ok, acknowledged - my fault, sorry. Problem solved …

 You couldn't have known – the port doesn't say anything about that.

 > I'm not sure, but a running (tcl) process survives the removal of its
 own binaries and scripts, as long as everything has already been loaded
 into RAM, or am I wrong ? Like when running the port-repl or the
 migration-script I mentioned above ?

 That might be true, but not every file needed might have been loaded at
 this point (even though the `package require` statements are usually at
 the top of our files, so that might even work).

 > Yep, have it already running on my second machine … good job so far. +1

 That's good to hear :)

 > Good spot, and/or to make it absolutely obvious rename “MacPorts” to
 “MacPorts-dev”?

 I've prevented installation of the MacPorts port with a very noisy message
 in r118259.

-- 
Ticket URL: <https://trac.macports.org/ticket/43085#comment:3>
MacPorts <http://www.macports.org/>
Ports system for OS X