After emerging app-cdr/nero and trying to run, it tells me the trial period already expired, and refuses to run. Not sure if this is a bug in the ebuild, but it's definitely a bug, because it prevents the user from testing the software.
Well, we need 2.0.0.4 in portage...
I tried renamimg the 2.0.0.3b-r2 ebuild to 2.0.0.4 and it worked fine.
*** Bug 116950 has been marked as a duplicate of this bug. ***
waiting for feedback on bug #113716 -- then I will bump it :)
*** Bug 117222 has been marked as a duplicate of this bug. ***
*** Bug 118385 has been marked as a duplicate of this bug. ***
Created attachment 76828 [details] nero-2.0.0.4.ebuild New ebuild for 2.0.0.4 - now installs to /opt/nero (Bug 89552) - fixed missing deps (Bug 113716); new use flag sox - fixed for modular X (Bug 115987) Please, test. Diff not attached, as it's basically complete rewrite. BTW, shorten should be local, not global use flag (it's not used by anything except nero).
nero-2.0.0.4.ebuild installs fine but nero fails to run, segmentation fault. Renaming 2.0.0.3b-r2 ebuild works so it may has something to do with not finding libraries in /opt/nero/usr/lib.
(In reply to comment #8) > Renaming 2.0.0.3b-r2 ebuild works so it may has something to do with not > finding libraries in /opt/nero/usr/lib. Well, all the libs are symlinked from /usr/${libdir} and /usr/share/nero to their respective locations in /opt/nero; if nero still can't find them then upstream really sucks.
Created attachment 77299 [details, diff] nero-2.0.0.4.ebuild.diff OK, /opt seems a no-go, back to /usr.
*** Bug 119422 has been marked as a duplicate of this bug. ***
2.0.0.4 should go into Portage this evening. Sorry for the delay.
=app-cdr/nero-2.0.0.4 committed.