[MacPorts] #30365: Additional option to selfupdate required if major changes take place
MacPorts
noreply at macports.org
Mon Jul 25 06:04:16 PDT 2011
#30365: Additional option to selfupdate required if major changes take place
--------------------------------+-------------------------------------------
Reporter: bgschaid@… | Owner: macports-tickets@…
Type: request | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.0.0
Keywords: | Port:
--------------------------------+-------------------------------------------
My confusion in #30302 came from the fact that
a) I wasn't aware that this wasn't a "port selfupdate" like every other
(update the port-list and minor updates)
b) the relevant point ("- Port images are now stored as archives. Archive
mode is now effectively ....") was number 23 in the release notes (if I
didn't miscount)
If I understand the release notes correctly this isn't going to happen in
the near future again. Nevertheless I'd suggest to modify the behaviour of
self-update in such a way that if it crosses certain version-numbers a
plain
port selfupdate
will fail with an error message like
"This selfupdate will upgrade your MacPorts from 1.8.3 to 2.1. This will
do major changes to the way MacPorts is organized. Please check the
release notes for 2.0 and make sure you understand them. Then proceed by
appending the option --upgrade-2.0 to 'port selfupdate'"
That would make sure that dimwits like me don't have the excuse "I didn't
read the ReleaseNotes because the upgrade hit me without warning".
--
Ticket URL: <https://trac.macports.org/ticket/30365>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list