From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RfC PATCH] gtk: switch to gtk3 by default, depricate gtk2.
Date: Thu, 07 Jul 2016 17:42:20 +0200 [thread overview]
Message-ID: <1467906140.6647.27.camel@redhat.com> (raw)
In-Reply-To: <20160707150419.GU31666@redhat.com>
Hi,
> > > + echo "If it is really your intention to build qemu with gtk2 re-run"
> > > + echo "configure with --with-gtkabi=2.0."
> > > + echo ""
> > > + exit 1
> > > fi
> > > fi
> >
> > I'm not really convinced that we should do this, though. Generally
> > configure should just work with what you have, unless you specifically
> > use options to ask it for a feature.
In general yes. But our plan is to remove gtk2 support. And I think it
is better to do this in two steps: First stop using it by default, with
gtk2 support still being available as backup plan in case there are
regressions[1] when people switch over to gtk3. Second actually
removing gtk2 support.
My main intention here is to catch cases where people build with gtk2
more or less by accident, something like package build dependencies not
being updated from gtk2 to gtk3 because qemu never demanded it.
> We could just print the message and then set gtk=no instead of 'exit 1'
Fine with me too.
But in that case people will probably notice it later, when they run
qemu and figure the gtk ui is gone. Not sure this is better than a
straight build failure. But at least they should easily find the
warning in the build logs when the start digging why gtk is gone.
cheers,
Gerd
[1] Not that I expect many problems given that fedora and probably other
distros too build with gtk3 for a while already.
prev parent reply other threads:[~2016-07-07 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 14:27 [Qemu-devel] [RfC PATCH] gtk: switch to gtk3 by default, depricate gtk2 Gerd Hoffmann
2016-07-07 14:32 ` Daniel P. Berrange
2016-07-07 14:52 ` Peter Maydell
2016-07-07 15:04 ` Daniel P. Berrange
2016-07-07 15:42 ` Gerd Hoffmann [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=1467906140.6647.27.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).