From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Fwd: Heads up for Qt5
Date: Sat, 28 Jul 2012 13:22:43 +0800 [thread overview]
Message-ID: <CAB9SyzT1=s88TWjuW7w3Kap6xe_0VsANEFSJ0=JL72-R1vYysg@mail.gmail.com> (raw)
In-Reply-To: <CAB9SyzSY0beKPpYE3fW93RP7TbBCoDvMOGDj8oa=pN_rEEkPmA@mail.gmail.com>
Hi!
We are getting nearer to a Qt5 beta release. Although it has already
been postponed a couple of times, we should expect it some time this
summer. This means we will start to see packages offering Qt5 support.
Pesa has already done a terrific job preparing live ebuilds and
eclasses for building Qt5 (tho maybe not all modules may be ready at
this point). They are available in our overlay. This should be a good
starting point for eventual release ebuilds that will hit the official
tree later.
In preparation for that, we want to ask maintainers of all ebuilds in
the tree with dependencies on Qt4, to make sure that they have the
proper slot. Otherwise your package may pull in Qt5 while it may not
in fact support it. Kensington has already done a good job, and is
presently being assisted by johu, going thru the tree, hunting for
such ebuilds. So you may get pinged about this issue if one of your
packages is affected.
We ourselves have made this oversight in the past in qt4-build.eclass,
which used to have unslotted blockers. This means that Qt5 was
actually blocked as well. Pesa fixed this a while ago, but people will
continue to have the unslotted blockers stored in their vdb until they
re-emerge or update all qt4 packages. Our apologies for the
inconvenience...
I also want to notify you that we will be using the "qt4" and "qt5"
useflags to indicate optional support for the respective Qt versions.
And finally, I want to thank all my fellow Qt team devs for making it
such a pleasure to work together on improving users' experience of Qt
libs and apps.
--
Cheers,
Ben | yngwin
Gentoo developer
Gentoo Qt project lead, Gentoo Wiki admin
next parent reply other threads:[~2012-07-28 5:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB9SyzSY0beKPpYE3fW93RP7TbBCoDvMOGDj8oa=pN_rEEkPmA@mail.gmail.com>
2012-07-28 5:22 ` Ben de Groot [this message]
2012-07-28 5:59 ` [gentoo-dev] Re: Fwd: Heads up for Qt5 Nikos Chantziaras
2012-07-28 6:27 ` Ben de Groot
2012-07-28 6:46 ` Davide Pesavento
2012-07-28 6:56 ` Nikos Chantziaras
2012-07-28 7:09 ` Davide Pesavento
2012-07-28 7:43 ` Ralph Sennhauser
2012-07-28 7:54 ` Ben de Groot
2012-07-28 9:27 ` Ralph Sennhauser
2012-07-28 10:07 ` Nikos Chantziaras
2012-07-28 13:57 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB9SyzT1=s88TWjuW7w3Kap6xe_0VsANEFSJ0=JL72-R1vYysg@mail.gmail.com' \
--to=yngwin@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox