The compile failure is cause by a move in the location of the libraries and headers. Please make mplayer R/DEPEND on lzo? ( =dev-libs/lzo-1* )
Created attachment 72799 [details, diff] files/mplayer-1.0_pre7-lzo2.patch for if/when mplayer does a revision bump and wants to depend on lzo2
This patch works perfect for me. I am not sure what packages still require /usr/lib/liblzo.so.1, but mplayer was the only package on my system that required this. It is always good to get rid of old stuff. Thanks, Ken
dependency changed =dev-libs/lzo-1* so that unmasking lzo-2 won't break this. lzo1 and lzo2 are slotted. Version with lzo2 support still required as per attached ebuild.
lzo support is going to be provided by libav, I'd drop the dependency once a snapshot with it will be in portage.
sounds good.
can this be closed?
(In reply to comment #6) > can this be closed? No, it still depends on =dev-libs/lzo-1*
(In reply to comment #7) > (In reply to comment #6) > > can this be closed? > > No, it still depends on =dev-libs/lzo-1* Hm, actually, the ebuild isn't in portage any more..
(In reply to comment #4) > lzo support is going to be provided by libav, I'd drop the dependency once a > snapshot with it will be in portage. Hmmm, can we drop the dependency now?
(In reply to comment #9) > (In reply to comment #4) > > lzo support is going to be provided by libav, I'd drop the dependency once a > > snapshot with it will be in portage. > > Hmmm, can we drop the dependency now? Actually I meant that pre7 ebuild (*mplayer*) isn't in portage any more.. I suggest the bug reporter checks if this problem persists with pre8 (and possibly this bug gets closed).
I just looked it up and mplayer ebuilds pre8 and newer still depend on lzo-1 while both verstions 1 and 2 are unmasked and not keyworded (for *most* archs). Unfortunately I have no idea if mplayer takes both ot uses the one from libav..
(In reply to comment #0) > The compile failure is cause by a move in the location of the libraries and > headers. > > Please make mplayer R/DEPEND on lzo? ( =dev-libs/lzo-1* ) D'oh, I really should do more reading and thinking here. In all three currently available ebuilds for mplayer, lzo-1 is defined as RDEPEND. So can this case be closed?
(In reply to comment #12) > In all three currently available ebuilds for mplayer, lzo-1 is defined as > RDEPEND. So can this case be closed? No. Please, re-read Comment #4
(In reply to comment #13) > (In reply to comment #12) > > In all three currently available ebuilds for mplayer, lzo-1 is defined as > > RDEPEND. So can this case be closed? > > No. Please, re-read Comment #4 Ok I see the point now I think. Sorry for the trouble.
MPlayer SVN now uses internal (libavutil) lzo for all features except one: For ve_nuv.c liblzo2 is used now, but there really should be very, very few people who actually want this encoder nowadays.
(In reply to comment #4) > lzo support is going to be provided by libav, I'd drop the dependency once a > snapshot with it will be in portage. > closing the bug