qemu-1.1.0+ bundles it's own version of libcacard and installs /usr/bin/vscclient when built with USE=smartcard which is also provided by app-emulation/libcacard: $ cave owner /usr/bin/vscclient app-emulation/libcacard-0.1.2::installed app-emulation/qemu-1.2.0::installed Comparing the versions reveals that the version in qemu has some fixes besides obvious adjustments (glib memory allocation for example and common qemu header includes). Sooo, unbundling is probably not that easy or desirable. Simple fix I applied to qemu-1.2.0 (since I was fixing some build issues with that ebuild anyway) was to rename the qemu vscclient to qemu-vscclient. If that's ok for you I'm going to apply this change to the other versions of qemu as well.
Well the qemu-1.2.0 ebuild is going to be chucked potentially when I finally get a good qemu 1.2.x series. As far as renaming, have we confirmed that doesn't cause any problems?
(In reply to comment #1) > As far as renaming, have we confirmed that doesn't cause any problems? Nothing in qemu directly depends on it nor is it a direct helper for qemu. The only problems a rename can cause is for someone who's already using it to do some ccid-card-passthru stuff. Since vscclient is run on the client I guess people will use libcacard as a provider for it rather than installing qemu on the client. But then I guess they are better off using spice to tunnel the smartcard data (since it offers TLS encryption of the traffic). Anyway I doubt there are many users since this bug is present for a couple of months already.
This is fixed in the tree using Tiziano's fix.
