Fwd: OpenAL Regressions In Intrepid

[Christopher Halse Rogers]

Argh.  Forwarding my mis-sent message because gmail sucks.

---------- Forwarded message ----------
From: Christopher Halse Rogers <chalserogers at gmail.com>
Date: Sep 24, 2008 12:58 PM
Subject: Re: OpenAL Regressions In Intrepid
To: Null Ack <nullack at gmail.com>


On 9/24/08, Null Ack <nullack at gmail.com> wrote:
 > Gday everyone,
 >
 >  The Linux Standard Base is surely a good thing. I don't know if OpenAL
 >  is included in the LSB or not. What I do know is that someone decided
 >  to change naming for OpenAL in Intrepid and this is causing many
 >  regressions in other apps that now can't find OpenAL.
 >
 >  Can I please refer people to this bug:
 >
 >  https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/273558
 >
 >  Some questions that come to mind are:
 >
 >  1. Why did we change the naming?


This one's easy to answer: Because the library's ABI changed.  This is
 also why the proposed solution of creating a symlink from
 libopenal.so.1 to libopenal.so.0 won't work.


 >  2. What is the best solution in the long term here for us?


Exactly what's happening now.  I note that libopenal0a is still
 installable - at least, I've got both libopenal0a and libopenal1
 installed, although it seems that the libopenal0a binary package has
 been removed from the archives in an Not-Built-from-Source sweep.
 It's possible that the Replaces: field doesn't do what you think it
 does (all it does is allow a package to overwrite a file provided by
 the Replaces'd package).

 Unless we want to keep the old source package around, producing an old
 OpenAL library, like we do for libstdc++5.  I think this would only be
 considered in exceptional circumstances, however - (almost) all the
 software in the repositories is now built against the newer library.
 Those packages still built against libopenal0a should have bugs filed
 against them - I'll get around to this later today if no one beats me
 to it.