qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: changing ROM bundling in tar dists for releases
Date: Fri, 01 Sep 2017 11:49:38 +0200	[thread overview]
Message-ID: <1504259378.10150.8.camel@redhat.com> (raw)
In-Reply-To: <20170901092407.GE31680@redhat.com>

  Hi,

> > Question is what to do with the non-firmware submodules (pixman,
> > dtc,
> > more?) then.  I think they are not that big, so I doubt it is worth
> > the
> > hassle to create two tarball versions.  And license-wise it isn't a
> > issue too.
> 
> I've always wondered why we need to specialcase those modules at all.
> Personally I'd just remove them entirely and let people install the
> -dev packages on their distro just like they do for any other build
> prerequisite of QEMU.

Yes, we can probably do that now with pixman.  A few years back when
the submodule was added there was the problem that some distros shipped
too old versions of pixman.  Known offender: RHEL-5.  But RHEL-5 is EOL
meanwhile and I think qemu raised the minimum glib version to something
newer than what RHEL-5 ships, so it qemu doesn't build on RHEL-5
anyway.

Dunno about dtc.

cheers,
  Gerd

  reply	other threads:[~2017-09-01  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 12:29 [Qemu-devel] RFC: changing ROM bundling in tar dists for releases Daniel P. Berrange
2017-08-31 12:49 ` Peter Maydell
2017-09-01  8:31   ` Gerd Hoffmann
2017-09-01  9:24     ` Daniel P. Berrange
2017-09-01  9:49       ` Gerd Hoffmann [this message]
2017-09-01 11:00       ` Peter Maydell
2017-09-01 14:11     ` Gerd Hoffmann
2017-09-01 15:13       ` Daniel P. Berrange
2017-09-01 17:45         ` Gerd Hoffmann
2017-08-31 15:47 ` Philippe Mathieu-Daudé

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=1504259378.10150.8.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).