Bug 111088

Summary: 6.2-REL mplayer package doesn't install libmp3lame.so.0
Product: Ports & Packages Reporter: David N <davidn04>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description David N 2007-04-01 10:50:07 UTC 
Running pkg_add -vr mplayer
then executing mplayer
/libexec/ld-elf.so.1: Shared object "libmp3lame.so.0" not found, required by "mplayer"
pkg_add -vr libmp3lame
or
pkg_add -vr lame
doesn't find the package

Fix: 

cd /usr/ports/audio/lame
make install

This will install nasm, make, gmake
How-To-Repeat: pkg_add -vr mplayer
then
running mplayer
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2007-04-01 21:50:49 UTC 
State Changed
From-To: open->feedback

Awaiting maintainers feedback
Comment 2 Thomas E. Zander 2007-04-02 04:40:09 UTC 
The problem with this is that due to licensing restrictions, we may not
provide a binary package for lame, but for mplayer we can. In addition
to the current workaround, i.e.

a) install lame from ports, then
b) install mplayer from $wherever

the only way I see to prevent the problem this pr is mentioning is to
exclude mplayer from binary packaging as well. As a result, it would
always be necessary to build both lame and mplayer from ports. This
seems even more uncomfortable to me.

Edwin, is there some general policy or porter's rule what to do in
such a case?

Riggs

-- 
- "[...] I talked to the computer at great length and
-- explained my view of the Universe to it" said Marvin.
--- And what happened?" pressed Ford.
---- "It committed suicide." said Marvin.
Comment 3 edwin 2007-04-02 05:25:18 UTC 
On Mon, Apr 02, 2007 at 05:40:09AM +0200, Thomas E. Zander wrote:
> The problem with this is that due to licensing restrictions, we may not
> provide a binary package for lame, but for mplayer we can. In addition
> to the current workaround, i.e.
> 
> a) install lame from ports, then
> b) install mplayer from $wherever
> 
> the only way I see to prevent the problem this pr is mentioning is to
> exclude mplayer from binary packaging as well. As a result, it would
> always be necessary to build both lame and mplayer from ports. This
> seems even more uncomfortable to me.
> 
> Edwin, is there some general policy or porter's rule what to do in
> such a case?

My suggestion is to make a slave-port called mplayer-nolame which
doesn't require audio/lame to be installed. That way mplayer can
be installed via a package without having to install audio/lame
manually.

Edwin

-- 
Edwin Groothuis      |            Personal website: http://www.mavetju.org
edwin@mavetju.org    |          Weblog: http://weblog.barnet.com.au/edwin/
Comment 4 Edwin Groothuis freebsd_committer freebsd_triage 2007-05-31 05:31:50 UTC 
State Changed
From-To: feedback->closed

According to maintainer, this is was fixed with ports/111980