[Buildroot] [PATCH 1/3] qemu-system: new package

[Arnout Vandecappelle]

On 12/10/14 21:03, Gustavo Zacarias wrote:
> 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: 

 Can you explain why not?

 You cannot use different versions for qemu-user and qemu-system in a clean way
if they're not different packages. But host and target versions don't need to be
the same. At least, I see code in pkg-generic.mk to handle that.

 And I do think we want to keep qemu-user and qemu-system at the same version,
right? Or does it happen that you need different versions for these as well?

 The real question is how to make the version depend on the values in
BR2_PACKAGE_QEMU_CUSTOM_TARGETS. But that is not the concern of your patch.


 Regards,
 Arnout


> 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.
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 
> 


-- 
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