From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: mplayer2 : focus deficiency?
Date: Wed, 10 Feb 2016 13:54:16 +0100 [thread overview]
Message-ID: <56BB32F8.5000201@mlbassoc.com> (raw)
In-Reply-To: <2021B186DC632746BD5A3CE32F12BD28011FB867B8@EU-MBX-02.mgc.mentorg.com>
On 2016-02-10 12:02, Belal, Awais wrote:
> Hi,
>
> The version of mplayer2 available in meta-oe is almost 2.5 years old while there seems to be active development around it. Is there a reason OE never moved to a newer version?
>
> The mplayer team officially releases tarballs from its website https://www.mplayerhq.hu/design7/dload.html while they also provide svn access through svn://svn.mplayerhq.hu/mplayer/trunk. I believe it would be a good idea to move to one of these sources (I would prefer tar downloads myself) and use a newer more robust (probably) version of mplayer2.
>
I didn't think to look anywhere other than their git tree which seems
to be abandoned (the version we are using is the latest out there)
> I will be working on a new recipe to cater this if there are no objections but I would really like to have some feedback before I do so.
I've been trying to fix up what we have now that OE-core has
abandoned libav, replacing it with a newer ffmpeg. Maybe I'll
give this a go myself if you'd like to wait a short while (perhaps
by tomorrow)?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-02-10 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 11:02 mplayer2 : focus deficiency? Belal, Awais
2016-02-10 12:54 ` Gary Thomas [this message]
2016-02-22 8:51 ` Belal, Awais
2016-02-10 13:10 ` Martin Jansa
2016-02-13 8:51 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56BB32F8.5000201@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox