On 25.08.2014 13:34, Ludwig Nussel wrote: > Andreas Färber schrieb: >> [...] >> Right now with Coolo's changes, both are building the exact same source >> code, but in two different places. It looks like QEMU's configure >> doesn't check for a system-installed libcacard today, which we/I should >> then fix upstream. My immediate concern however was whether those two >> packages, qemu and libcacard, could run out of step without qemu.spec >> growing an BuildRequires on libcacard-devel - may understanding is no, >> due to the indirect dependency through spice, but a second pair of eyes >> would be appreciated. > > AFAICT spice doesn't depend on qemu, only on libcacard. So it would be > fine to treat libcacard like an independent package and make qemu build > against that one too. The current way of building the lib internally > again looks a bit odd but I doubt that it has any practical > implications. So either way is fine. > Not building it twice (but buildrequire) removes the risk that the 2 libcacards get binary incompatible by means of configure switches or build environment.
If you can live with that risk, using the make system everyone uses and build twice is the safer choice. Greetings, Stephan -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
