[Bug 1030] Review request: xbmc - Media center
http://bugzilla.rpmfusion.org/show_bug.cgi?id=1030
--- Comment #105 from Jonathan Dieter <jdieter(a)gmail.com> 2010-03-01 14:36:53 ---
I would really like to see a number of the libraries in xbmc/lib split out and
packaged separately (preferably in Fedora).
The ones I'm looking at are:
* cximage (could go into Fedora, I think)
* libcmyth (could also go into Fedora as it doesn't need to actually be built
against MythTV, at least as far as I can see).
* libexif (mentioned earlier, already in Fedora)
* libhdhomerun (already in Fedora)
* libid3tag (already in Fedora, not sure if it includes fixes mentioned in
xbmc/lib/libid3tag/readme.txt)
* librtmp (could go into Fedora, I think)
* libshout (already in Fedora)
* libsquish (could go into Fedora unless there are patent problems, not sure
myself)
* libupnp (aka Platinum UPnP, could go into Fedora)
* libxdaap (based on libopendaap, could either package fork or push changes
back upstream)
* UnrarXLib (can we ditch this and include patches to move to libunrar?)
I'd also like to see xbmc using system library headers whenever possible rather
than bundled headers:
* boost
* libglew
* libiconv (though /usr/include/iconv.h is totally different from the bundled
one; don't know how that works!)
* libportaudio (though we're missing pa_mac_core; unneeded for Linux, perhaps?)
* sqLite (it seems to be the sqlite3 header and some code having to do with
datasets; if we can at least ditch the header, that would be great)
* zlib
Finally, the following may not be appropriate for Fedora or RPM Fusion because
of problematic licenses:
* libGoAhead (Not quite sure what to make of the license, but I think this is
going away in the next release anyway)
* libhts (Not sure where upstream is or what it's licensed under)
I would happily review any of these that need to go into either Fedora or RPM
Fusion, and will also try to help split some of these out.
--
Configure bugmail: http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.