All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Olaf Hering" <olaf@aepfle.de>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Fam Zheng" <famz@redhat.com>,
	"QEMU Trivial" <qemu-trivial@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"open list:All patches CC here" <qemu-devel@nongnu.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v1] configure: require glib-2.24
Date: Thu, 19 Apr 2018 10:23:20 +0100	[thread overview]
Message-ID: <20180419092320.GJ10259@redhat.com> (raw)
In-Reply-To: <20180419092017.olujzxzlwvjlt6en@sirius.home.kraxel.org>

On Thu, Apr 19, 2018 at 11:20:17AM +0200, Gerd Hoffmann wrote:
>   Hi,
> 
> > Well, it depends. You might be stuck with an old distro because
> > some software you want to run depends on it, but also want to run
> > newer versions of some programs like QEMU. If you're in that
> > boat you can probably live with having to also compile a newer
> > version of glib to go with your newer QEMU, though.
> 
> Core libraries like glib might not be that easy, I've seen updating glib
> breaking apps in the past.

You would likely just have to build it all into /opt/qemu so it is
isolated from whatever the distro included. 

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|


  reply	other threads:[~2018-04-19  9:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 12:38 [Qemu-trivial] [PATCH v1] configure: require glib-2.24 Olaf Hering
2018-04-18 12:45 ` [Qemu-trivial] [Qemu-devel] " Cornelia Huck
2018-04-18 12:55   ` Daniel P. Berrangé
2018-04-18 14:41     ` Cornelia Huck
2018-04-18 14:43       ` Daniel P. Berrangé
2018-04-19  7:19     ` Markus Armbruster
2018-04-19  7:30       ` Olaf Hering
2018-04-19  7:59         ` Daniel P. Berrangé
2018-04-19  8:54           ` Peter Maydell
2018-04-19  9:01             ` Kamil Rytarowski
2018-04-19  9:20             ` Gerd Hoffmann
2018-04-19  9:23               ` Daniel P. Berrangé [this message]
2018-04-18 14:45   ` Olaf Hering
2018-04-18 12:47 ` Daniel P. Berrangé
2018-04-18 13:00   ` Olaf Hering
2018-04-18 13:29   ` Peter Maydell
2018-04-18 14:44     ` Daniel P. Berrangé
2018-04-26  8:17       ` Peter Maydell
2018-04-26  9:19         ` Thomas Huth
2018-04-26  9:54           ` Peter Maydell
2018-04-26 11:52         ` Paolo Bonzini
2018-04-26 12:08           ` Olaf Hering
2018-04-26 12:10             ` Daniel P. Berrangé
2018-04-26 12:11               ` Olaf Hering
2018-04-26 12:39                 ` Paolo Bonzini
2018-04-26 12:42                   ` Paolo Bonzini
2018-04-26 12:42                   ` Olaf Hering
2018-04-26 12:12             ` Peter Maydell
2018-04-18 13:34   ` Eric Blake
2018-04-18 12:53 ` no-reply
2018-04-18 13:04   ` Olaf Hering

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=20180419092320.GJ10259@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=olaf@aepfle.de \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.