[MacPorts] #49086: Bad user experience if user forgets to save a list of requested ports before OS upgrade
MacPorts
noreply at macports.org
Mon Oct 5 04:04:14 PDT 2015
#49086: Bad user experience if user forgets to save a list of requested ports
before OS upgrade
--------------------------+--------------------------------
Reporter: macports@… | Owner: macports-tickets@…
Type: enhancement | Status: closed
Priority: Normal | Milestone:
Component: base | Version: 2.3.4
Resolution: invalid | Keywords:
Port: |
--------------------------+--------------------------------
Comment (by graziosi.angelo@…):
Replying to [comment:3 ryandesign@…]:
> You are welcome to "migrate" a slightly different way (this is what I
did last year when I updated from Mavericks to Yosemite): upgrade OS X,
install new Xcode, reinstall MacPorts base, but do not uninstall all
ports. Instead, use "sudo port upgrade" to upgrade the outdated
ports—which will be all of them. Some ports will fails to build for the
reasons you mentioned, but the previous versions might continue to work.
There are other reasons why these upgrades might fail, including that you
might have to upgrade ports in a particular order. If you encounter an
error, carefully read the error messages in the main.log and see if it
might point to a particular port that you should upgrade first.
>
> If you want a smooth upgrade experience, you should wait before
upgrading OS X and not upgrade on day 1... Give us some time to fix the
issues first.
Sorry, but I am not subscribed there...
> If you'd like to discuss further, the macports-users mailing list is a
better place than in a ticket.
OK, the users could refrain from upgrading to the new OSX but this does
not resolve the basic problem.
Yesterday I followed your suggestion, and did a smooth upgrade
{{{
sudo port upgrade xz
sudo port upgrade harfbuzz
sudo port upgrade libtheora
sudo port upgrade iTerm2
sudo port upgrade atool
sudo port upgrade aspell
sudo port upgrade aspell-dict-en
sudo port upgrade aspell-dict-it
sudo port upgrade dos2unix
sudo port upgrade unrar
sudo port upgrade lftp
sudo port upgrade tesseract-eng
sudo port upgrade tesseract-ita
sudo port upgrade p7zip
sudo port upgrade djvu2pdf
sudo port upgrade pdf2djvu
sudo port upgrade clamav
sudo port upgrade allegro5-devel
sudo port upgrade gv
sudo port upgrade plotutils
sudo port upgrade xfig
sudo port upgrade xorg-server
sudo port upgrade root6
sudo port upgrade at-spi2-core at-spi2-atk
sudo port upgrade gdk-pixbuf2
sudo port upgrade emacs-mac-app
}}}
These were only requested packages and all have been upgraded. The only
packages which failed were:
{{{
pdftk
geant4 (qt4-mac)
djview (qt4-mac)
}}}
It took more than 12 hours.. more then 12 hours to "upgrade" what already
worked fine: installed under Yosemite and working under El Capitan. And
this only because MacPorts says:
{{{
cloog 0.18.3_0 < 0.18.3_0 (platform darwin 14 !=
darwin 15)
djview 4.10_0 < 4.10_0 (platform darwin 14 !=
darwin 15)
gcc47 4.7.4_5 < 4.7.4_5 (platform darwin 14 !=
darwin 15)
[...]
}}}
I think we should have only "one" installer, MacPorts-2.3.4.pkg, and only
packages which do not depend on darwinXY,
{{{
emacs-mac-app @5.9_0+imagemagick+rsvg.darwin.tbz2
[...]
}}}
After a new OSX release if there is some package that do not work, it
would be upgraded when the fix has been found.. without constrain the
users in upgrading what really already works..
Ciao,
Angelo.
--
Ticket URL: <https://trac.macports.org/ticket/49086#comment:4>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list