The new release is at, http://people.fedoraproject.org/~jwrdegoede/v4l-utils-0.7.91.tar.bz2 Notice how Fedora also jumped from 0.6.4 to the new 0.7.91 package here, http://cvs.fedoraproject.org/viewvc/rpms/libv4l/devel/ This new tarball seems to contain also utilities, among the libraries. I'm not sure if we want to make a new ebuild, like media-video/v4l-utils or just keep using the media-libs/libv4l... also I hate the idea of splitting the package, since it's shipped as one by upstream.
If I understand it right, 0.7.91 is a beta package. As for utilities, see the announcement at http://lwn.net/Articles/376592/ for more details. Basically, for no good reason that I can see, Hans de Goede decided to bundle libv4l with a bunch of v4l and dvb utilities into a single tarball. My feeling is that we should have separate libv4l and v4l-utils ebuilds (that use the same source tarball). Some of the reasons include: * That's what Debian and Fedora are doing. * No need to adjust existing dependencies or create a virtual. * Almost everyone who has a modern webcam (i.e. almost everyone who has a modern laptop) needs libv4l to make use of their hardware. By contrast, few people will ever need utilities like decode_tm6000 ("decodes tm6000 proprietary format streams") or v4l2-compliance ("tool to test v4l2 API compliance of drivers"). The target users for the library and the utilities are completely different. * libv4l has no dependencies beyond libc. By contrast, one of the utilities depends on qt.
bumped libv4l tools -> new package -> new bug -> ebuild attached, thanks :-p heh
