MediaInfo supplies technical and tag information about a video or audio file. It is free software (free of charge and free access to source code: GPL or LGPL licence) Reproducible: Always
Created attachment 211298 [details] ebuild, works fine with USE="-curl -libmms"
Created attachment 213447 [details] new version, renamed ebuild
Created attachment 217017 [details] new version, renamed ebuild
Created attachment 223999 [details] new version, re-structured ebuild Thanks Nikoli for your initial ebuilds, I've now done a version which is more "Gentoo-ish" by splitting off ZenLib and MediaInfoLib into separate ebuilds which install their pkgconfig info and headers: dev-libs/libzen media-libs/libmediainfo This also solves the issues with running configure in the proper ebuild phase of EAPI 2. Still does not compile with curl and libmms though.
Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Thanks, On behalf of the Gentoo Sunrise Team, Justin. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
I think separating is not necessary now: libzen and libmediainfo is used only by mediainfo-cli or mediainfo-gui, my ebuild builds them statically if only cli or gui is chosen. Or may be you know some projects that use these libraries and we should compile them as shared?
(In reply to comment #6) > I think separating is not necessary now: libzen and libmediainfo is used only > by mediainfo-cli or mediainfo-gui, my ebuild builds them statically if only cli > or gui is chosen. Or may be you know some projects that use these libraries and > we should compile them as shared? Well, you're saying "now", and I admit, I do not know of other projects, but nevertheless, if only for solving the warnings during emerging mediainfo and keeping smaller, well-defined packages (those libs are already packaged separately by upstream, I did not split them just because I wanted, they were already, so I thought why not take advantage of that) which might be used in future by other projects and then one does not have to change package structure again, it would be already prepared for this. Just my opinion.
Created attachment 225719 [details] fixed: SRC_URI, added static build option, use pkg-config instead of broken lib*-config, libmms, dll does not work and we do not need it
Lucian, agree, thanks for helping with splitting. But please check your ebuilds more carefully. Now for me all USE combination's work fine, may be it is time for including in portage? Please test them.
Created attachment 231467 [details] new version Lucian, please obsolete your ebuilds for this package and deps.
Created attachment 232003 [details] some fixes
in CVS (finally), thanks guys for help
*** Bug 255179 has been marked as a duplicate of this bug. ***
If I can ask a stupid question here, why is this keyworded ~amd64 only? It seems to build (and run) fine on x86.
Please keyword it as ~x86.
