Re: [MacPorts] #43085: MacPorts 2.3 »beta« already released via selfupdate ?

[MacPorts]

#43085: MacPorts 2.3 »beta« already released via selfupdate ?
------------------------------+--------------------------------
  Reporter:  stephan.jorek@…  |      Owner:  macports-tickets@…
      Type:  defect           |     Status:  new
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.2.1
Resolution:                   |   Keywords:
      Port:                   |
------------------------------+--------------------------------

Comment (by stephan.jorek@…):

 Replying to [ticket:43085 stephan.jorek@…]:

 >…
 >This message suggests you have the MacPorts port installed. You should
 not
 >install the MacPorts port, it's only for developers to create the binary
 >installers they re-distribute to users.

 Ok, acknowledged - my fault, sorry. Problem solved …


 >MacPorts should always be updated using selfupdate, and it's entirely
 >possible installing the MacPorts port has overwritten the files
 previously
 >installed by the MacPorts installer without running the required post-
 >setup scripts that avoid the problem you are mentioning. Didn't you have
 >to force-activate the MacPorts port when you installed it?

 Yes, I had to force-activate it (and did a clean-up afterwards). And I
 have to admit, that I used the macports-migration reinstall-script from
 http://trac.macports.org/wiki/Migration . So, it was my fault …


 >If you
 >uninstall the MacPorts port now that will likely break your MacPorts
 >installation, because it will remove the files required to run MacPorts.

 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 ?

 >I suggest you make a backup of `/opt/local`, uninstall the MacPorts port
 >and run the 2.3.0-beta1 installer (see
 >https://lists.macosforge.org/pipermail/macports-
 dev/2014-March/026208.html). Going back to 2.2.x is probably not a good
 >idea now, because the layout of the database changed (and the beta seems
 >pretty stable at the moment, so it's not worth the risk).

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

 > We should really prevent the MacPorts port from installing (and
 > overwriting MacPorts' files).

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

 Thanks for your immediate reply,

 Stephan

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