KR> When would you update the version string? Anytime a change goes KR> into libvirt-cim, there's a possibility that the change in KR> behavior will affect the test case. If you want to update a test KR> so that it behaves one way for libvirt releases older than x.x.4 KR> and a different way for releases x.x.4 and higher, then you'd need KR> to update the embedded string every time you check in a changeset. KR> Unless I'm missing what you mean here. Well, I think it's probably appropriate to embed the actual version number (i.e. 0.4) as well as the changeset number. KR> Ideally, it'd be nice to use the hg changeset number, but I'm not KR> sure how to make that happen. There are ways :) I'll see about a patch. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com