Red Hat Bugzilla – Bug 316731
RFE: Please update libao to 0.8.8 version
Last modified: 2007-11-30 17:12:17 EST
Notable changes since 0.8.6:
- the 'alsa' device now uses the 0.9/1.0 API
- ALSA driver fixes
What is even more important: 0.8.8 supports PulseAudio, which is now the default
in Fedora. So I think this package should be updated ASAP.
Created attachment 250291 [details]
I have updated the specfile to 0.8.8, at the same time cleaning it up a bit.
I'm not sure if the kludges present are still needed, so I left them in.
Updated library seems to work correctly, it even pick PulseAudio as a default
driver for some reason. Changes:
- Updated to 0.8.8
- Cleaned up the SPEC
- Added PulseAudio support
- Made build parallel
- Killed rpaths
- Changed the kludges to use sed
Hans, Behdad told me to CC you as the vorbis stack comaintainer.
(In reply to comment #3)
> Hans, Behdad told me to CC you as the vorbis stack comaintainer.
Behdad, may I ask why? Do vorvis stack parts need a rebuild for this, or is this
considered part of the stack too? I guess judging from the download URL, that it
is. So I'm guessing you want me to become co-maintainer of libao too? Which is
fine by me. I'll be filing a request for the necessary changes in packagedb
right after this comment.
Please ack wether or not I guessed your intentions right.
Julian, thanks for the improved specfile, I've used it verbatim. I've also added
the following changes:
* Wed Nov 14 2007 Hans de Goede <email@example.com> - 0.8.8-2
- Fix multilib conflict (bz 341891)
- Fix Source0 and URL urls
0.8.8-2 is now building and should show up in tomorrow's rawhide. Since this
also adds pulseaudio support I will also be pushing it as an F-8 update.
libao-0.8.8-2.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update libao'
libao-0.8.8-2.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.