As discussed on Monday, adding the libvirt-qmf package to Fedora is dependent on having an updated version of matahari to build against. Since the process of adding a package may take some time and the deadline is looming, I think we will need to do two rebases of matahari - one for an API-stable version that libvirt-qmf can list a dependency on, and another with all of the features scheduled for F16.
Andrew (or Russell), can you give an Ack or Nack on those patches I sent yesterday ASAP please? Since they change the API and the locations of header files, I need to know whether they are in or out before delivering the libvirt-qmf patches.
Once that is settled and a rebase of the matahari package in Fedora from upstream is done, I can deliver those changes and move forward on creating the package. In the meantime I will work on getting the spec file into shape on the assumption that the next matahari release will be 0.5.0.
We can then do a second rebase of matahari to pull in further non-API-breaking stuff (e.g. Adam's sysconfig work) before the F16 deadline. Are there any objections to that plan?
thanks, Zane.