Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new package: libav
Date: Wed, 06 Jul 2011 07:14:18 +0200	[thread overview]
Message-ID: <87k4bwuh1x.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110705224642.4953b847@skate> (Thomas Petazzoni's message of "Tue, 5 Jul 2011 22:46:42 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 >> - 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>

 Thomas> Could you turn this into a proper commit log message ? Could you also
 Thomas> send your patch inline and not as an attached file ? This make it
 Thomas> easier to review and comment.

Yes please - Please use git format-patch -s / git send-email

 Thomas> If the libav package is a copy of the ffmpeg one, isn't it
 Thomas> possible to share the same .mk file ? We could then make them
 Thomas> separate when/if libav diverges from ffmpeg in a significant
 Thomas> way.

I haven't followed the libav discussions in detail - Is it (currently) a
100% drop in replacement for ffmpeg? If so, perhaps we should handle it
like the modular/tinyx selection for the X server. If not, I think it
should be two completely independent packages.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-07-06  5:14 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
2011-07-06  5:14   ` Peter Korsgaard [this message]
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=87k4bwuh1x.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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