Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] qemu-system: new package
Date: Mon, 20 Oct 2014 21:41:34 +0200	[thread overview]
Message-ID: <5445656E.9010404@mind.be> (raw)
In-Reply-To: <54446B1B.2090201@zacarias.com.ar>

On 20/10/14 03:53, Gustavo Zacarias wrote:
[snip]
> To me it seems the decision was taken during the dev days with one-sided
> arguments (against), but well life is like that sometimes.

 Well, there was nobody to provide counter-arguments. That's why I started the
discussion on the list.

 It's very clear that version selection is needed. It's not so clear that a
separate version is really needed for host-qemu-system and host-qemu-user, because:

 - there's a slightly larger chance that both system and user are broken;
 - we currently anyway don't have version selection for user;
 - we can change it later if required.

 On the other hand, it's also possible to merge the qemu-system package now and
refactor it back into a single package later. It wouldn't even require legacy
handling because the config symbols already start with BR2_PACKAGE_QEMU.

 So I'd propose to give Yann some time to produce a unified qemu package, but if
it doesn't come we can still merge your original patch.

> The side effect is that it pushes my motivation to contribute to
> buildroot to an all-time low (read that as you wish, in fact it may not
> even matter).

 Since you're the #1 buildroot contributor and have been for some time now, it
really does matter!


 Regards,
 Arnout
-- 
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-10-20 19:41 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
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 [this message]
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=5445656E.9010404@mind.be \
    --to=arnout@mind.be \
    --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