Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report.
Summary: Review Request: AllegroOgg - Ogg library for use with the Allegro game library
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188625
j.w.r.degoede@hhs.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO|163779 |163778 nThis| |
------- Additional Comments From j.w.r.degoede@hhs.nl 2006-04-29 04:46 EST ------- There wasn't much discusion, so I'm going to "fix" this by doing things as suggested in my initial proposal to the list:
So there we are 2 different ogg support for use with allegro support libraries both installing:
/usr/lib/libalogg.so
One of them installs: alogg.h
And the other: alogg/alogg.h
Which also seems like an accident waiting to happen. I'm thinking of solving this by:
-give AllegroOGG a new soname: libAllegroOGG.so, or should I give them both a new name, and in that case what should I use for alogg? -putting all the header files of both in seperate dirs under include: /usr/include/allog/(alogg/alogg.h) /usr/include/AllegroOGG/(allogg.h) -modifying allog-config todo the right thing for alogg -use pkgconfig for AllegroOgg -patch AllegroOGG using programs to use pkgconfig. Currently only raidem can use AllegroOGG (I have a new version ready which adds ogg support as a replacement for the stripped out mp3 support, giving raidem its background music back).
I'll post links to a new specfile and SRPM once I'm done, in the mean time I'm resetting this to FE-REVIEW :|
package-review@lists.fedoraproject.org