Gerd Hoffmann <kra...@redhat.com> writes: > On 09/25/12 12:48, Peter Maydell wrote: >> On 25 September 2012 11:37, Gerd Hoffmann <kra...@redhat.com> wrote: >>> On 09/25/12 11:31, Peter Maydell wrote: >>>> For me "not a standard library package on RHEL5" is a strong argument >>>> against adding a hard dependency. (For instance, most of the compute >>>> cluster machines here are RHEL5 and it would be pretty awkward to >>>> deal with manually building a dependent library.) >>> >>> Why it is that a big deal? Whatever is used to distribute qemu to the >>> cluster machines (local yum repo?) can be used to distribute pixman too, no? >> >> There's a big leap between "run configure, put the qemu executable >> in some generally available directory" and "you have to first get >> and build some third party library, install it somewhere, tell >> configure where you put it, then build qemu, then make sure that >> not just the qemu executable but also this third party library >> are on all the machines". At the moment you can build qemu without >> any non-system dependencies, and we should have a really good >> reason for breaking that. > > Hmm, we could import a pixman copy into the qemu tree and use that as > fallback if we don't find pixman installed on the system ...
We can include a pixman submodule in qemu.git and have configure try to find a local version, if it's not available, build the embedded version. After RHEL5 becomes ancient, we can simply remove the submodule. Should make everyone happy. Regards, Anthony Liguori > > cheers, > Gerd
