From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new package: libav
Date: Tue, 5 Jul 2011 22:46:42 +0200 [thread overview]
Message-ID: <20110705224642.4953b847@skate> (raw)
In-Reply-To: <0LvAri-1Rcapv3sjy-010LQJ@mrelayeu.kundenserver.de>
Hello Wolfram,
Thanks for your patches!
Le Fri, 01 Jul 2011 18:27:13 +0200,
Wolfram Gloger <wg@malloc.de> a ?crit :
> This is a copy of the ffmpeg package with the names and download
> changed for libav-0.7.
>
> Why choose this fork when there is "original" ffmpeg?
>
> - It may be the future? I don't know, but for sure it was dreadfully
> hard to get patches into ffmpeg.
>
> - I found that ffmpeg (at least 0.6.3) does _not_ work with minidlna
> (buildroot patch forthcoming), there are strange hangups just
> calling av_stream_info() on many ts files.
> libav worked out of the box in this context.
>
> Signed-off-by: Wolfram Gloger <wg@malloc.de>
Could you turn this into a proper commit log message ? Could you also
send your patch inline and not as an attached file ? This make it
easier to review and comment.
If the libav package is a copy of the ffmpeg one, isn't it possible to
share the same .mk file ? We could then make them separate when/if
libav diverges from ffmpeg in a significant way.
What do you think ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-07-05 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 16:27 [Buildroot] [PATCH] new package: libav Wolfram Gloger
2011-07-05 20:46 ` Thomas Petazzoni [this message]
2011-07-06 5:14 ` Peter Korsgaard
2011-07-06 6:51 ` Thomas Petazzoni
2011-07-06 7:22 ` Peter Korsgaard
2011-07-13 16:21 ` Wolfram Gloger
2011-07-13 16:10 ` Wolfram Gloger
2011-07-13 16:16 ` Thomas Petazzoni
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=20110705224642.4953b847@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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