Created attachment 289647 [details] gst-plugins-kate-0.10.22.ebuild This ebuild installs the Kate plugins that are part of the GStreamer BAD plugins. I tested it on my Gentoo box and it worked perfectly. I put this ebuild, along with its Manifest and metadata files, in an Portage Overlay I created locally and emerged it with "emerge -v gst-plugins-kate".
I forgot to mention that this is an alternative (better?) aproach to resolve bug #386697. Oh, and the ebuild I sent was based on the ebuild for "gst-plugins-faac".
Created attachment 289649 [details] Manifest file for gst-plugins-kate
Created attachment 289651 [details] Metadata file for gst-plugins-kate
Please do not add cc on your own.
*** Bug 386697 has been marked as a duplicate of this bug. ***
It's generally not necessary to attach Manifest files for these. It will be recreated anyhow. In this case metadata.xml wasn't important either, particularly because theoretically you don't know for sure that gstreamer herd will maintain this (but it will, because bumps/stabilization need to be done all at once by us, main packages and split packages all together) but helpful to have if it documents local USE flags though. Also ACCEPT_KEYWORDS should contain ~arch keywords (not stable) of arches you have actually really tested the ebuild/package/functionality. I doubt you have tested it on all of alpha, amd64, ppc, ppc64 and x86 and it's probably what was in the gst-plugins-faac ebuild. The ebuild should probably somehow handle the automagic libtiger dependency aswell. I'll take care of all that with my own version of the ebuild once I get to it, but hope these comments are useful for hopefully continued further ebuild contributions on bugzilla from you :)
Thank you, Mart. In future ebuils I will take into account everything you said. And yes, those arch keywords where in the "gst-plugins-faac" ebuild. I only tested it on AMD64. And it is still working fine. :P After reading "man 5 ebuild" more carefully I learned that I could include the libtiger dependency if libkate was not found, since only one of them is required for the plugin to be built: || ( media-libs/libkate media-libs/libtiger ) But of course you already knew that. :)
No, it's not an OR dependency. It's an optional automagic dependency for an additional tiger element to be built for the kate plugin, which uses the tiger library for subtitles rendering, while without it you only get the katedec, kateenc and such elements with which the rendering would be done purely by GStreamer. I believe with tiger one can get various effects and animations support working with kate subtitles, but I'm clarifying that. At any rate, we need to handle the dep properly, and currently it's an inconvenient "automagic" one, which means we need to either always depend on it, or actually patch configure* to make it tweakable by arguments passed (for us ending up with something like a $(use_enable tiger) thing). That's because otherwise it would automatically link to it in any case, and if we don't have the dependency recorded in package manager, then the package manager would allow to uninstall libtiger, and if it was present at the time of gst-plugins-kate compilation, the whole plugin gets broken. (Though with the portage-2.2_alpha's it wouldn't actually remove libtiger.so files, but that's also suboptimal).
Is this ever going to make it into the main tree? Otávio, could you explain how to create the local overlay?
(In reply to spacexplosion from comment #9) > Is this ever going to make it into the main tree? > > Otávio, could you explain how to create the local overlay? I'm sorry spacexplosion, but I just don't remember how to create the overlay anymore. I switched from Gentoo to Arch Linux about 2 years ago. You can try following the instructions at "http://wiki.gentoo.org/wiki/Overlay/Local_overlay" for creating a local overlay.
I wanted to add this today but libtiger and libkate are not multilib compatible.
Pushed to tree with 1.8.3 bumps. This is limited to abi_x86_64 though since opencv is not multilib aware.
