From: Ralph Sennhauser <sera@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Fwd: Heads up for Qt5
Date: Sat, 28 Jul 2012 09:43:09 +0200 [thread overview]
Message-ID: <20120728094309.2152ef42@sera-17.lan> (raw)
In-Reply-To: <CAB9SyzSxSd09L7h9O6F=wVMFAAT4x--vZAgPRTCY4_O6E2dUXA@mail.gmail.com>
On Sat, 28 Jul 2012 14:27:49 +0800
Ben de Groot <yngwin@gentoo.org> wrote:
> On 28 July 2012 13:59, Nikos Chantziaras <realnc@gmail.com> wrote:
> > On 28/07/12 08:22, Ben de Groot wrote:
> >>
> >> 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.
> >
> >
> > This can be trouble if the application actually works with Qt5. It
> > might depend on Qt4 but has no problems with Qt5 (contrary to Qt3
> > vs Qt4, Qt5 is mostly compatible with much of existing Qt4 code),
> > needlessly pulling-in Qt4. Many applications simply build and run
> > as-is and no code changes are necessary.
> >
> > So what would be the methodology of making sure a package has the
> > proper slot?
>
> Obviously you would need to make sure that the package actually does
> support Qt5. Then, as I see it, we could do either:
>
> || ( x11-libs/qt-gui:4 x11-libs/qt-gui:5 )
Never prefer an old version in an || ( ) block, this makes for a poor
update experience. Also the || ( ) construct can only be used if they
are runtime switchable, which I really doubt here, as otherwise you
build against one, the user install the other and portage depcleans the
one you have built against.
>
> or:
>
> qt4? ( x11-libs/qt-gui:4 )
> qt5? ( x11-libs/qt-gui:5 )
>
A qt5 useflag will do more harm than good. If I enable qt, I do not
care which version, I just want the gui for the particular app. If the
app works with qt:5 the usflag qt means qt:5, if it only works with
qt:4 the useflags means qt:4. In case it works with both and the
maintainer thinks it's worth to let the user choose, use the useflag qt4
to let the user opt out of the latest and greatest.
> Other thoughts?
next prev parent reply other threads:[~2012-07-28 7:44 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 ` [gentoo-dev] Fwd: Heads up for Qt5 Ben de Groot
2012-07-28 5:59 ` [gentoo-dev] " 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 [this message]
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=20120728094309.2152ef42@sera-17.lan \
--to=sera@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