> || ( > ( dev-qt/qtcore:4 dev-qt/qtgui:4 ) > ( dev-qt/qtcore:5 dev-qt/qtgui:5 ) > ) This won't work - Qt slots aren't interchangeable.
You're referring to the fact that an || dependency can be swapped out, right? And that gecode will break if you upgrade from qt4 to qt5? If so, I think all we need to do is add subslot deps: gist? ( || ( ( dev-qt/qtcore:4 dev-qt/qtgui:4 ) ( dev-qt/qtcore:5 dev-qt/qtgui:5 ) ) <dev-qt/qtcore-6:= <dev-qt/qtgui-6:= )
This will trigger a useless rebuild on every major Qt version bump. From qtcore's metadata.xml, subslots: Must only be used by packages that are known to use private parts of the Qt API. We should follow the rest of the tree by either forcing one version of Qt, or introducing USE flags. See https://wiki.gentoo.org/wiki/Project:Qt/Policies#Handling_different_versions_of_Qt for more details.
In addition to automagically selecting a Qt version to build against (with subsequent runtime breakage), this package also: * Has a similar automagic selection and breakage with gmp/mpir * Fails to respect CFLAGS correctly * Installs source files to the root directory * Installs html documentation to the wrong directory (html/html)
It also bundles and installs its own copy of boost.
I've fixed most of these. I'm not sure if there's anything we can do about boost, and other distros ship it that way too. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=16f2c13fa964bad248df33231fb2fff2a6b6e5ad
Thanks. The only thing preventing the removal of the 3.x version is dev-ruby/dep_selector. It looks like there was a commit on August 3rd upstream to support gecode 4.x, and a new release on rubygems.org on August 5th. With any luck, that new release will support gecode-4.x and we can drop the old one.
