i just want to use the engine NMM in amarok , when i try to compile amarok1.3.6 with ./configure --with-nmm then i have this error : make[5]: *** [nmm_engine.lo] Error 1 make[5]: Leaving directory `/var/tmp/portage/amarok-1.3.6/work/amarok-1.3.6/amarok/src/engine/nmm' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/var/tmp/portage/amarok-1.3.6/work/amarok-1.3.6/amarok/src/engine' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/tmp/portage/amarok-1.3.6/work/amarok-1.3.6/amarok/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/amarok-1.3.6/work/amarok-1.3.6/amarok' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/amarok-1.3.6/work/amarok-1.3.6' make: *** [all] Error 2 !!! ERROR: media-sound/amarok-1.3.6 failed. !!! Function kde_src_compile, Line 217, Exitcode 2 !!! died running emake, kde_src_compile:make !!! If you need support, post the topmost build error, NOT this status message. i modified the ebuild .. from --without-nmm to --with-nmm, but then i still need NMM which is actually NOT in portage, you can get some ebuild from this location : http://www.networkmultimedia.org/NMM/Download/Gentoo/index.html but i dont want it that way... next time i emerge sync these ebuilds will eventually disappear and all together its looking like time wasting too, to watch all the steps to configure it manually... is there maybe a security related issue with NMM or why are these ebuilds not yet in portage ? THX a lot , have a nice sunday...
Don't restrict bugs without any reason.
Created attachment 95025 [details] ebuild for nmm ebuild find on http://stephane.barotin.free.fr/nmmstable.php
why it isnt in portage already ?
The upstream of NMM is now http://www.motama.com/nmm.html , however it seems the latest available release came out in May 2013 and I couldn't actually get it to compile. Not to mention the fact the ebuild posted here is completely incompatible with nmm-2.3.0 anyway.
In light of lack of comments for 4 months now, I assume there is indeed no user demand for this package. Closing the bug.