qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 4/7] libcacard: initial commit


From: Jes Sorensen
Subject: Re: [Qemu-devel] [PATCH 4/7] libcacard: initial commit
Date: Wed, 16 Mar 2011 09:26:57 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7

On 03/15/11 16:14, Alon Levy wrote:
> On Tue, Mar 15, 2011 at 03:59:26PM +0100, Jes Sorensen wrote:
>> I don't think it is necessary for distro packaging. Most distros will
>> build multiple binary packages from one source package, and it is up to
>> the user to decide which ones to install.
> 
> if someone has the prerequisites for building libcacard, but not for building
> qemu, they should be able to build just libcacard. You can achieve this by
> having flags specifically, or by just behaving like we behave for features in
> general, that is not building qemu if it can't be. I think the first option is
> cleaner because it also allows requesting just libcacard (even if you do have
> the prerequisites for building qemu).

I don't think it is such a big issue, in most cases people will pull in
their distro libraries with yum or apt before they start building their
user app. It is standard distro packaging practice to generate multiple
packages from one source package.

On the other hand I don't think it would be a problem if you submitted
patches to the QEMU configure/Makefile setup that allowed for building
just the libraries and disabling the QEMU binaries. I don't see distros
using this, but end developers might.

Cheers,
Jes



reply via email to

[Prev in Thread] Current Thread [Next in Thread]