public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Johannes Huber <johu@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Supporting both Qt4 and Qt5 builds
Date: Tue, 12 Aug 2014 00:33:18 +0200	[thread overview]
Message-ID: <2661087.J9LNJ0BdB7@dutt> (raw)
In-Reply-To: <CAGbUWSKf=6iRiGf7ByL45jfvF+vo26pxGCqrb2Vy0AxzoqtXAA@mail.gmail.com>

Am Sonntag, 10. August 2014, 14:51:45 schrieb Georg Rudoy:
> 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? The pros and cons for each, off
> the top of my head:
> 
> slotting:
> + Allows having different use flags for qt4 and qt5 builds (can't
> think why that would be needed in the above examples though).
> - Possibility of exponential growth of the number of slots in case
> slotting would be required according to some other criteria (again,
> can't think why that would be needed in the above examples).
> - Requires keeping two different copies of the same ebuild with
> basically the same build rules, with all the consequences.
> 
> useflags:
> + Seems to be easier and doing the required trick.
> + app-text/poppler already does this.
> - Enabling support for previously disabled Qt version requires
> rebuilding the whole library twice.
> 
> What's your opinion on this?
> 
> I've attached the useflag-based variant as a draft.

Multibuild is prefered.

-- 
Johannes Huber (johu)
Gentoo Linux Developer / KDE Team
GPG Key ID F3CFD2BD



  reply	other threads:[~2014-08-11 22:33 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 [this message]
2014-08-12  5:28 ` Ben de Groot

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=2661087.J9LNJ0BdB7@dutt \
    --to=johu@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