Hi, There is two version available for each platform : the allplatform version (the one the ebuild use) and the performance pack. This one contains extra files like lib for v4l and things like that. Without them you cant really use jmf like you want (it is my opinion :) Is there a reason why this version was chosen instead of the performance pack one ? Is it possible to have the ebuild use it, or maybe add a use flag for it ? Thanks :] Reproducible: Always Steps to Reproduce: 1. 2. 3.
Seconded. I'd prefer to not have to install anything outside portage, but I really do need v4l capturing functionality from JMF.
I looked into this a little, and think it might be a bit problematic. It is only available in a self-extracting script, which in addition to extracting, does stuff like probe v4l devices, and opens some X11 stuff. The script could feasibly be modified to not do that, but the license suggests that something like this is prohibitted.
Is anyone planning on working on this?
Went into the same problem here. I think it is mostly a licensing problem as nichoj said :(
(In reply to comment #4) > Went into the same problem here. I think it is mostly a licensing problem as > nichoj said :( > Yah I gave up on the JMF. There has been no update in years and the license sucks. Found a few open source alternatives and what I could not find I will produce from scratch.
jmf-bin is ancient and has been masked for removal.
jmf-bin has been removed a while ago. Closing.