Re: [email@example.com: Bug#114274: libarts-alsa: will not drive alsa]
On Wed, Oct 03, 2001 at 05:45:33PM -0600, Ivan E. Moore II wrote:
> On Wed, Oct 03, 2001 at 12:05:23PM -0400, Gordon Tyler wrote:
> > I guess then the fault lies with alsa and it's packaging. It shouldn't allow
> > an old library that is incompatible with the newer kernel modules to
> > co-exist.
> how is it supposed to know and why should they not co-exist? libasound1 and
> libasound2 do not have the same files...so there is no need for them
> to conflict. This allows folks like me to develop for libasound2 while keeping
> a functional libasound1 system.
But libasound1 uses the alsa 0.5 device protocol whereas libasound2 uses
the alsa 0.9 device protocol. If you have the alsa 0.9 driver modules
installed, then libasound1 is useless. But yes, I can see your point about
how is it supposed to know, since the alsa driver modules have to be
compiled and installed separately and they don't have an identifiable
package name that the libasound* could depend/conflict on.
So I guess what I'm trying to say is that the bug reporter's problem is
that he probably has the alsa 0.9 driver modules installed which don't work
with libarts yet.