libdc1394-2.1.0 released. I've writ ebuild and introduced new use-flag 'usb' in it, which adds dependency to >=dev-libs/libusb-1.0, which is not in portage tree... Juju support selects in runtime in new libdc1394, but I've left use-flag 'juju' for dependency >=sys-kernel/linux-headers-2.6.23-r3 and add '+' before it. I've tested it with old and new firewire stacks with dc1394 cameras, all works fine. Reproducible: Always
Created attachment 180701 [details] media-libs/libdc1394-2.1.0.ebuild
And Stefan Richter also said (https://sourceforge.net/mailarchive/message.php?msg_name=49871165.8040403%40s5r6.in-berlin.de) that "libdc1394 v2 calls into libraw1394 only if the old kernel drivers are active. If the new kernel drivers are active, libdc1394 performs everything through its own interface to firewire-core." What do you thing about it? Maybe dependency on libraw1394 may be omitted if some use flag is off, "ieee1394" for example?
> Maybe dependency on libraw1394 may be omitted if > some use flag is off, "ieee1394" for example? Upstream libdc1394 v2 does not have a ./configure switch to build it without libraw1394 (+ video1394) backend, i.e. a downstream modification would be necessary to implement that. However, there is almost nothing to gain from that, and something valuable to lose: The ability to fall back to the old kernel driver whenever desired or necessary.
The Juju flag and the dependency on kernel-headers can and should be removed; they are not applicable to libdc1394 v2.1.0 and later.
Sorry this has been lying around for so long... Committed media-libs/libdc1394-2.1.0.
