From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new package: libav
Date: Wed, 6 Jul 2011 08:51:40 +0200 [thread overview]
Message-ID: <20110706085140.749b6388@skate> (raw)
In-Reply-To: <87k4bwuh1x.fsf@macbook.be.48ers.dk>
Le Wed, 06 Jul 2011 07:14:18 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> 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.
My understanding is that libav is a fork of ffmpeg. So, it will
probably become more and more different than ffmpeg, in which case
separate packages are obviously the right way of handling this.
In the mean time, as they are exactly similar (at least in terms of
build mechanism and options), I wanted to suggest doing a modular/tinyx
style of selection. We might switch to a separate package when needed.
But on the other hand, having a separate package is probably more clear.
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-06 6:51 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
2011-07-06 6:51 ` Thomas Petazzoni [this message]
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=20110706085140.749b6388@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