From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Supporting both Qt4 and Qt5 builds
Date: Tue, 12 Aug 2014 13:28:56 +0800 [thread overview]
Message-ID: <CAB9SyzRLjr75f368r2YuvgQhifAaA0Wc0vraxGCG9d+udWWBgA@mail.gmail.com> (raw)
In-Reply-To: <CAGbUWSKf=6iRiGf7ByL45jfvF+vo26pxGCqrb2Vy0AxzoqtXAA@mail.gmail.com>
On 10 August 2014 18:51, Georg Rudoy <0xd34df00d@gmail.com> wrote:
> Hi,
>
> I'm thinking of converting a few ebuilds (x11-libs/qwt,
> dev-libs/kqoauth, net-libs/qxmpp among them) to support building with
> both Qt4 and Qt5.
>
> Should this better be done by adding the corresponding useflags (qt4
> and qt5 respectively) or by slotting?
>
> What's your opinion on this?
>
The Qt team has always recommended the useflag method for packages
that support more than one major version of Qt. This is also what we
implement ourselves. So for consistency's sake, please stick with the
useflags.
--
Cheers,
Ben | yngwin
Gentoo developer
prev parent reply other threads:[~2014-08-12 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 10:51 [gentoo-dev] Supporting both Qt4 and Qt5 builds Georg Rudoy
2014-08-11 22:33 ` Johannes Huber
2014-08-12 5:28 ` Ben de Groot [this message]
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=CAB9SyzRLjr75f368r2YuvgQhifAaA0Wc0vraxGCG9d+udWWBgA@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