[MPlayer-users] mandrake software inclusion policy

[Guillaume Rousse]

Hello avifile & mplayer developers.

As you already know, i'm currently maintaining avifile and mplayer package 
for Mandrake that can't be included officially for copyright/patent problems:
- only support for windows dll in both package
- lame plugin in avifile
- gsm code in avifile (not compatible with gpl)

However, i just received a quick resume of mandrake software inclusion policy:
>Basically the main rules are:
>- the main must be self buildable 
>- the main and contrib must be self buildable
>- the main must not depend on something not in main
>- the main and contrib must not depend on something neither in main nor 
>contrib
>- everything in main and contrib must be freely or commercially
>distributable, modifiable, patchable, and preferably with a free software
>license or alike (GPL, BSD...)
>- any ambiguous situation regarding copyright or patent enfridgment must
>be solved with not includind the program.
>
>As a consequence, any tool linked to non free java virtual machine
>could not be included, any softwares that include mp3 Fraunhofer
>copryrighted encoder or encoder likely to infridge Fraunhofer mp3
>encoding algorythms must not be included. But any software that do not
>include incriminated algorythms but that accepts downloadable plugins
>can be included (e.g. vlc)

So i was wondering it it was possible to build avifile/mplayer wich could 
satisfy contrib requirement, using ffmpeg for divx support, not including 
problematic parts but making them available as external packages. So, i would 
like your opinion on the following issue:
1) is this possible ?
2) is this worth the try ?
-- 
Guillaume Rousse <rousse at ccr.jussieu.fr>
GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html