Opened 15 years ago

Closed 15 years ago

#17619 closed enhancement (fixed)

Consider removing the dp2mp upgrade code from base

Reported by: jmpp@… Owned by: jmroot (Joshua Root)
Priority: Normal Milestone: MacPorts 1.8.0
Component: base Version: 1.8.0
Keywords: dp2mp move upgrade darwinports dports Cc: raimue (Rainer Müller)
Port:

Description

I looked around Trac but didn't find any ticket pertaining to my following proposal: we should start considering removing the dp2mp upgrade code from base (both base/Mk/macports.upgrade.mk and base/portmgr/dmg/preflight), as it's been quite a while since MacPorts 1.5.0, released on 09-July-2007, which is when my code saw the light of day.

The one big problem with this is that, if there happen to be any such incredibly-lagged-behind-stragglers, we'd be breaking any upgrade compatibility with them, for both their installed MacPorts release and their installed ports (i.e., they might as well rm -rf ${prefix}), given how extensively I changed the installation layout in the dp2mp move. So if we still want to make it smooth for them, we'd have to *explicitly* document a two-step upgrade process for them:

  1. Installation from the last dmg containing the upgrade code, but *NOT* from anything newer than that;
  2. Selfupdating to the latest release;

Ideas...?

-jmpp

Change History (4)

comment:1 Changed 15 years ago by jmpp@…

Summary: Consider removing dp2mp upgrade code from baseConsider removing the dp2mp upgrade code from base

comment:2 Changed 15 years ago by raimue (Rainer Müller)

Cc: raimue@… added
Keywords: darwinports dports added

comment:3 Changed 15 years ago by jmroot (Joshua Root)

Owner: changed from macports-tickets@… to jmr@…
Status: newassigned

comment:4 Changed 15 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: assignedclosed

Done in r53260. Now we just check for ${prefix}/etc/ports/dp_version and error out if it's present, with a message saying to install 1.7.1 first.

Note: See TracTickets for help on using tickets.