force specific Qt5 version install?
Michael Dickens
michaelld at macports.org
Fri Apr 5 19:30:55 UTC 2019
Thank you, Ryan, for that info. I'll have to poke at the Qt5 PortGroup more & see what it says about OSX 10.12 and 10.13 since that's where my current issues are.
A quick followup from yesterday for this issue on OSX 10.13: I was surprised that "port" did indeed "update" -all- of Qt5 from 5.12 to 5.11; it took a few internal iterations of "rev-upgrade", but it did succeed eventually.
Here's my wondering today about this Qt5 issue, on my OSX 10.12 boot:
{{{
% uname -a
Darwin mpbr15-10-12 16.7.0 Darwin Kernel Version 16.7.0: Wed Feb 27 00:29:57 PST 2019; root:xnu-3789.73.43~1/RELEASE_X86_64 x86_64
$ port version
Version: 2019-03-23
[MLD NOTE: I build "port" from "base" GIT master, and use the date of the commit for the version in "config/macports_version"; this is the current latest GIT master commit.]
$ port outdated
The following installed ports are outdated:
qt5-qtbase 5.12.1_0 < 5.12.2_0
qt5-qtsvg 5.12.1_0 < 5.12.2_0
[MLD NOTE: This is correct!]
$ sudo port clean qt5*-qtbase qt5*-qtsvg
Password:
---> Cleaning qt5-qtbase
---> Cleaning qt55-qtbase
---> Cleaning qt56-qtbase
---> Cleaning qt57-qtbase
---> Cleaning qt58-qtbase
---> Cleaning qt59-qtbase
---> Cleaning qt511-qtbase
---> Cleaning qt5-qtsvg
---> Cleaning qt55-qtsvg
---> Cleaning qt56-qtsvg
---> Cleaning qt57-qtsvg
---> Cleaning qt58-qtsvg
---> Cleaning qt59-qtsvg
---> Cleaning qt511-qtsvg
[MLD NOTE: This is -not- correct: qt512 doesn't even show up now!]
$ sudo port -p upgrade qt5-qtbase qt5-qtsvg
---> qt5-qtbase is replaced by qt511-qtbase
---> Computing dependencies for qt511-qtbase
Error: Can't install qt511-qtbase because conflicting ports are active: qt5-qtbase
---> qt5-qtsvg is replaced by qt511-qtsvg
---> Computing dependencies for qt511-qtsvg
Error: Can't install qt511-qtsvg because conflicting ports are active: qt5-qtbase
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
[MLD NOTE: This is -not- correct. Also: I generally don't use "-p" but here I know each port would fail already so I used it just to let "port" try to update.]
}}}
Looking at the file "_resources/port1.0/group/qt5-1.0.tcl", I see for this OS (os.major == 16):
{{{
} elseif { ${os.major} == 16 } {
#
# macOS Sierra (10.12)
#
# Qt 5.12: Supported
# Qt 5.11: Supported
# Qt 5.10: Supported
# Qt 5.9: Supported
# Qt 5.8: Supported
# Qt 5.7: Not Supported but seems to work
#
return qt5
#
}}}
.... so ... not sure why "port" thinks qt511 is the way to go here. I'll admit that I didn't poke through the rest of this code, so maybe elsewhere this value is ignored / overloaded / overwritten?
Anyway, seems a little fishy here ... - MLD
More information about the macports-dev
mailing list