On 8.5.2017 15:24, Helio Chissini de Castro wrote:
Hello everyone.
So we ( @kdesig ) started to update Qt to 5.9 on Rawhide as will be the
target for next Fedora release.
5.8.x is already been dephased by upstream and 5.9.0 already reach beta
3 stage.
Hi, one of my packages just FTBFS because:
Error: nothing provides qt5-qtbase(aarch-64) = 5.8.0 needed by
python3-qt5-5.8.2-1.fc27.aarch64
Can python3-qt5 5.8 be built against 5.9? Or do we need 5.9 as well?
Thank you.
At this moment the update is not ready due some PPC build issues for
qt5-qtdeclarative packages, but we already are working on it, so we ask
a little patience until fix the issue and the rawhide packages depending
on Qt will be out of sync until we manage to fix this issue.
Among the new things, there's a new proposal package for documentation
as a whole. Explaining:
Qt documentation became more and more hard to build among all the
several modules since internally each doc has references for other doc
modules,
and this lead me to try a complicated approach on previous 5.8.x build.
Each package during the build of their doc, need to depend of one or
more doc modules.
This made the whole process complex, far from be perfect, and forced us
to bootstrap several modules and compile twice.
So, for this release, we agreed on the kdesig meeting to try the
approach of a single generated doc package, as recommended by Qt upstream.
Is basically a documentation generated from the source code of all
modules at same time.
This lead us to have a single package, with all info properly synced and
with all references, conforming the Fedora guidelines to have a "binary"
blob.
The package is in review here
https://bugzilla.redhat.com/show_bug.cgi?id=1448451
We will be happy to receive comments about this new approach.
Regards, Helio
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
