So wait, there won't be h.264 for pandora? I figure it'd come naturally as part of the Community Codec PND and mplayer, or if someone cared to, compiling ffmpeg or x264 directly. I know Chromium uses ffmpeg for HTML5 support which uses webkit, and the browser we plan on using also uses webkit. Not sure at what point webkit meets ffmpeg... but I suppose someone will crap out a Chromium PND eventually, or I could just make one myself... Considering ffmpeg and Chromium and the dependence on each other, how will dependencies be dealt with? Will I just have to provide it in the PND or would I be able to have an ffmpeg PND and a Chromim PND and the Chromium one would just require the ffmpeg one? I imagine if you have a lot of packages that have a lot of the same dependencies, you end up with the issues a lot of Windows programs have where you have 100 copies of the same .DLL.
Optimally, the Community Codec PND would install ffmpeg separately so we don't have this issue with regard to codecs. Though maybe the runtime linker by default should be made to look in a directory on the SD cards for other libraries people may need, and not have to fill up the NAND with.
Eh, this has just been a rant as to how I think things should be. Probably bullshit, blah blah blah.