[oe] [PATCH] mplayer_svn: Package can be built again; Bumped to rev. 31329.

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 22-01-11 14:31, Lars Michelsen wrote:
> Hello,
> 
>>> A recipe can have multiple svn sources, so you can fetch ffmpeg into a
>>> seperate directory then move it into the mplayer one overwriting
>>> whatever mplayer checked out.
>>
>> Ffmpeg isn't using svn anymore, so if mplayer is using svn remote, it
>> won't get updated since last week.
> 
> wow, things are changing fast. I checked out the current mplayer repo
> and it still fetches the svn repositories. But we are using old
> revisions - so this would be OK for the moment.
> 
> In a long term the mplayer_svn package could be replaced by mplayer_git
> package. mplayer_git could make use of ffmpeg git repo then, right?
> 
> So what does this mean for the mplayer_svn patch? Should I invest time
> to make it use several subversion repositories instead of the sub
> repositories?

Looking closer at your patch, it looks like you're working off an old tree:

http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=9a3e44e3d3d69ab9e1e4e1e3338afaed2b97fb65

Your patch is also missing the hardfp fix that is needed to actually
make it work.

Could you try the current recipe and see if it works for you? It works
on my omap3 boards quite well, minus a dlopen() buglet in libdvdcss2.

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNOvT2MkyGM64RGpERAjJ+AJ4uFl1okywMkeiI5qkWnLAFL4cPJgCfR0TZ
ihgltc+c8QBUGwoyvE3uu5U=
=I/6U
-----END PGP SIGNATURE-----