On Wed, Apr 19, 2017 at 01:08:19PM +0100, KatolaZ wrote:
> On Wed, Apr 19, 2017 at 12:44:32PM +0100, ael wrote:
>
> [cut]
> >
> > Unhappily, I am still using debian, and my testing was done on unstable.
> > Obviously I did not invoke mpv (etc) with "apulse mpv", so I was
> > disturbed with it linking to libpulse-simple.so nevertheless.
> > This was on a system with no pulseaudio, only alsa. Maybe putting apulse
> > in its own folder will fix things.
>
> This is where apulse comes in the scene: if a program requires
> pulseaudio, apulse will lure it into believing that pulseaudio is
> available, but behind the scenes it will use ALSA instead. This is

I have been experimenting with apulse and am confused.

If I build from source using the "default" instructions, the
libraries seem to be installed in /usr/local/lib/ rather than a
"special hidden" directory. Since /usr/local/lib is specified in
/etc/ld.so.conf.d/libc.conf, this is on the default library path.

However, if I use
cmake -DAPULSEPATH=/usr/local/lib/apulse -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Release ..

then the apulse libraries are properly "hidden" in /usr/local/lib/apulse.

I didn't seem anything like this in the rules for the Devuan package.
Did I miss where this is specified?

My problems with mpv and mplayer would be explained if this is an
oversight in the apulse build. Although it is possible to explicitly
specify the audio-device as alsa for these programs, the README.md
file suggests that they should not have tried to use the apulse
libraries.

Where does the devuan apulse package install
libpulsecommon-5.0.so,libpulse-simple.so,libpulse-simple.so.0,libpulse.sio
and libpulse.so.0?

Your earlier email suggested that it was somewhere special.

ael