#17619: Consider removing dp2mp upgrade code from base --------------------------------+------------------------------------------- Reporter: jmpp@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts 1.8.0 Component: base | Version: 1.8.0 Keywords: dp2mp move upgrade | Port: --------------------------------+------------------------------------------- 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 -- Ticket URL: <http://trac.macports.org/ticket/17619> MacPorts <http://www.macports.org/> Ports system for Mac OS