Charles A Edwards <[EMAIL PROTECTED]> writes: > I maintain my systems at current cooker using urpmi so I have both > libalsa1 and libalsa2 installed and there was no conflict during > installation.
and what ? libalsa1 is useless now. > Those programs that now require .so.2 operate properly as do those > that still require .so.1, so I do not see the problem. no these either fallback on oss or won't works with sound. > Not to mention the fact that libalsa2 is kernel dependent and is > listed as belonging to the system/kernel and hardware group,where as > libalsa1 is not kernel dependent and belongs to the system/libraries > group. NO! libalsa1 is dependant of kernel alsa-0.5.x whereas libalsa2 is dependant on kernel alsa-0.9.x. you can have libalsa withouth an alsa aware sound driver. but having libalsa1 when you know that no more driver is using 0.5.x api is useless -- "il a ete brule au 28e degre" (the naheulbeuk witch) "c curieux, gcc fonctionne" (gwenole)
