From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] qemu-system: new package
Date: Sun, 12 Oct 2014 16:03:44 -0300 [thread overview]
Message-ID: <543AD090.3000107@zacarias.com.ar> (raw)
In-Reply-To: <20141012171752.29414e94@free-electrons.com>
On 10/12/2014 12:17 PM, Thomas Petazzoni wrote:
> We discussed this patch series during the Buildroot meeting. PATCH 3/3
> is Superseded, as you have updated the Qemu defconfigs many time since
> then.
>
> Regarding PATCH 1/3 and PATCH 2/3, we continue to believe it should be
> part of the qemu package itself, and not a separate qemu-system. Since
> I know you are not interested in doing this work, Yann E. Morin has
> said he was interested in doing this, once his current patch series
> adding support for qemu-system on the target has been merged.
>
> Consequently, I will mark your patches as 'Changes Requested' in
> patchwork. Of course, if in the mean time you change your mind and
> decide to implement host qemu-system as part of the qemu package, we'd
> be happy to receive your patches! :-)
I don't agree on the reasoning:
You can't use different versions for host and non-host packages in a
clean way: that alone and the fact that no single qemu version can cover
all of the emulations would make the single package pointless.
It's all fine and nice to strive to get qemu fixed but it's an
unrealistic objective, new architectures and variants together with old
emulations that seldomly are used/tested will continue to make this a
moving target.
Time and time again this has proven to be the case so leaving a fixed
version for the package will make it pointless, we can just tell people
to use some random distro version and get the same result which would
render the host package with no sense to be.
And changing the package version for the target because the host version
needs some special care plays into the changing results arena.
Granted it's not a common use-case to have both, but it's doing it
regarless.
You want all emulations to work, not just some depending on weather,
wind and pollen count.
So on my side i'm not planning to do anything with this decision.
Regards.
next prev parent reply other threads:[~2014-10-12 19:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 20:20 [Buildroot] [PATCH 1/3] qemu-system: new package Gustavo Zacarias
2014-05-03 20:20 ` [Buildroot] [PATCH 2/3] configs/qemu: update for host-qemu-system Gustavo Zacarias
2014-05-03 20:20 ` [Buildroot] [PATCH 3/3] configs/qemu: bump relevant kernel/header versions Gustavo Zacarias
2014-10-12 15:17 ` [Buildroot] [PATCH 1/3] qemu-system: new package Thomas Petazzoni
2014-10-12 19:03 ` Gustavo Zacarias [this message]
2014-10-15 17:01 ` Arnout Vandecappelle
2014-10-16 13:53 ` Gustavo Zacarias
2014-10-17 22:47 ` Arnout Vandecappelle
2014-10-18 1:14 ` Gustavo Zacarias
2014-10-19 20:27 ` Arnout Vandecappelle
2014-10-19 20:54 ` Thomas Petazzoni
2014-10-20 1:53 ` Gustavo Zacarias
2014-10-20 19:41 ` Arnout Vandecappelle
2014-10-20 21:16 ` Thomas Petazzoni
2014-10-20 22:45 ` Gustavo Zacarias
2014-10-21 7:16 ` Thomas Petazzoni
2014-10-21 18:20 ` Yann E. MORIN
2014-10-22 10:23 ` Peter Korsgaard
2014-10-21 19:45 ` Arnout Vandecappelle
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=543AD090.3000107@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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