Bug#469397: ITP: xbmc -- XBox Media Center Linux Port

[Andres Mejia]

Strange, I never received the last email.

Anyway, to answer your question, xbmc uses a modified form of ffmpeg 0.5. I'm not 
sure how much modifications it has as of right now, or whether we can make it 
possible to build xbmc to depend on system libs of ffmpeg.

xbmc has a random release schedule at best. The next release is scheduled in 5 
months, but that's not definite. Check [1].

I also want to mention something else here. It is the number of libraries that I 
see xbmc uses internally or build-depends on.

Build-Depends: debhelper (>= 5), python-support, autotools-dev, libdbus-1-dev,
 libhal-dev, libhal-storage-dev, make, g++-4.1, gcc-4.1, libsdl1.2-dev,
 libsdl-image1.2-dev, libsdl-gfx1.2-dev, libsdl-mixer1.2-dev,
 libsdl-sound1.2-dev, libbz2-dev, libcdio-dev, libfribidi-dev,
 liblzo-dev,liblzo2-dev, libfreetype6-dev, unzip, libsqlite3-dev, libogg-dev,
 libsmbclient-dev, libasound2-dev, python2.4-dev, python2.4, python-sqlite,
 cmake, libglew1.5-dev, libcurl3-dev, gawk, x11proto-xinerama-dev,
 libxinerama-dev, libxrandr-dev, libxrender-dev,
 libmms-dev, pmount, libtre-dev, libvorbis-dev,
 libmysqlclient15-dev, libpcre3-dev, libbluetooth-dev, libfontconfig-dev,
 libcwiid1-dev, libboost-dev, libtool, zip, nasm, autoconf, automake,
 libjasper-dev, libxt-dev, libxmu-dev, gperf, libenca-dev, libjpeg62-dev,
 libpng12-dev, dpatch
Internal-Build-Depends: 
 libsidplay2-dev,
 libdumb1-dev,
 timidity,
 python-dev,
 libid3tag0-dev | libid3tag-dev,
 libexif-dev,
 libprojectm-dev,
 liblame-dev [just-for-regular-support],
 libfaac-dev [just-for-regular-support],
 libdvdnav-dev [heavily-patched],
 libavcodec-dev [regression],
 libavformat-dev [regression],
 libavutil-dev [regression],
 libpostproc-dev [regression],
 libswscale-dev [regression],
Possible-External-Build-Depends: 
 libdts-dev,
 libfaad-dev,
 liba52-0.7.4-dev | liba52-dev,
 libmpeg2-4-dev,
 libmad0-dev,
 libass-dev,
 libmpcdec-dev,
 libflac-dev,
 libwavpack-dev,
Maybe-Build-Depends:
 goom,
 rss-glx,
 hdhomerun,
 cximage,
 libadpcm-dev,
 monkeys-audio [macdll],
 nosefart [nsfcodec],
 snes-apu [snesapu],
 gym-codec [gensapu],
 libvgmstream-dev,
 libshnplay-dev,
 stsound [ymcodec],
 libalac-dev,
 libadplug-dev,

Here's what I mean by the various fields. The 'Build-Depends' field is a list of 
packages that xbmc depends on during build on that can be found in the Debian 
archive already.

'Internal-Build-Depends' are packages that can be found in the Debian archive, 
but in which xbmc uses it's own internal version. The tag [just-for-internal-
support] next to a package means that xbmc can build without that package. The 
tag [regression] means I had xbmc build depending on the system libs of these 
packages at one point, but was later broken by some change within the linuxport 
branch of xbmc in their svn. For libdvdnav, xbmc uses a heavily modified version 
of libdvdnav in which there's possibly no way to have it use the system version 
of libdvdnav, unless upstream were to accept the patches from xbmc. For all 
other packages in this field, I have not had the time to go through and see if 
it's possible to build xbmc using the Debian packages instead.

For the 'Possible-External-Build-Depends', these are packages for where it's 
possible to build XBMC using the respective Debian package.

Finally, for the 'Maybe-Build-Depends' field, these are packages where xbmc uses 
it's own internal version, and which either do not exist in the Debian archive, 
or do not have the appropriate version in Debian.

As far as what system packages instead of internal packages I think xbmc should 
use, they should all the packages listed, except for the ones in the 'Maybe-
Build-Depends'.

1. http://xbmc.org/trac/roadmap

-- 
Regards,
Andres