Unable to install dosbox because of conflict with mplayer?

[Bryan Blackburn]

On Sat, Dec 20, 2008 at 11:49:57AM -0500, Tim Visher said:
> Hello all,
> 
> I'm trying to get dosbox and mplayer installed.  I already sent a
> message about the issue I'm having with MPlayer but I'm also
> discovering an issues with dosbox.  This is strange, because I just
> had both of these packages installed but had to deactivate them to get
> upgrades to work correctly.  Anyway,  I'm encountering the following
> when attempting to install dosbox:
> 
>     [~]$ sudo port install -f dosbox
>     --->  Installing speex @1.0.5_0
>     Error: Target org.macports.install returned: Registry error: speex
> @1.0.5_0 already registered as installed.  Please uninstall it first.
>     Error: The following dependencies failed to build: libsdl_sound speex
>     Error: Status 1 encountered during processing.
> 
> The reason I'm using the -f flag is because dosbox had previously
> reported the following:

Using force (-f) can have odd results, like this, when you start dealing
with dependencies as well; it's really best to use force only in certain
specific cases, and only when dealing with one port at a time, so using it
for install can be risky at best.

> 
>     [~]$ sudo port install dosbox
>     Password:
>     --->  Installing speex @1.0.5_0
>     --->  Activating speex @1.0.5_0
>     Error: Target org.macports.activate returned: Image error:
> /opt/local/bin/speexdec is being used by the active speex-devel port.
> Please deactivate this port first, or use the -f flag to force the
> activation.
>     Error: The following dependencies failed to build: libsdl_sound speex
>     Error: Status 1 encountered during processing.
> 
> It seems that there may be some sort of weird multi-branch dependency
> that port can't figure out how to resolve between dosbox and mplayer?

It sounds like you already have speex-devel installed (which is the
in-development version compared to speex), so it makes sense that speex
would conflict with it.

As a dependency, the best way to deal with this would be to update the
libsdl_sound port (which is what wants speex) to also allow speex-devel by
using a path:some/file/speex/installs:speex so it can make use of an
already-installed speex-devel.  Someone who knows more about libsdl_sound
and speex would need to determine if this is in fact feasible.

Bryan


> 
> Anyway, help would be appreciated.
> 
> -- 
> 
> In Christ,
> 
> Timmy V.
> 
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail