Qt4 is dead and going away, SoQt master apparently switched to CMake and already builds with Qt5 instead by default.
In theory, yes, unfortunately upstream is messing with extracting common buildsystem and project stuff now to separate projects (akin to git submodules), this requires some custom src_unpack to fetch symlink those deps.. and doesn't work anyway because some files are missing according to CMake or misplaced. I might need to take some trial & error approach to find commit that works.
Thanks for your update; together with emfengine and quarter this is quickly becoming one of the very last blockers of qt4-removal.
Tuesday mask day.
Created attachment 537278 [details]
The attached ebuild depends on coin-9999 which is not in tree. I suggest a small change to fix that:
It would be nice if the SoQt mask could mask only qt4 dpendend versions
The mask can be adjusted as soon as a relevant ebuild would be in tree.
The bug has been closed via the following commit(s):
Author: Andreas Sturmlechner <email@example.com>
AuthorDate: 2018-07-01 16:52:01 +0000
Commit: Andreas Sturmlechner <firstname.lastname@example.org>
CommitDate: 2018-08-07 07:27:04 +0000
media-libs/SoQt: Remove last-rited
media-libs/SoQt/Manifest | 1 -
media-libs/SoQt/SoQt-1.5.0-r1.ebuild | 57 ----------------------
.../SoQt/files/SoQt-1.5.0-pkgconfig-partial.patch | 13 -----
media-libs/SoQt/metadata.xml | 10 ----
profiles/package.mask | 1 -
5 files changed, 82 deletions(-)
Closing this bug solved the qt4 removal.
But pivy (bug 659478) requires the newer SoQt ebuild attached to this bug.
Should I open a new bug?
(In reply to bug2017 from comment #8)
> Should I open a new bug?