From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new package: libav
Date: Wed, 13 Jul 2011 18:16:26 +0200 [thread overview]
Message-ID: <20110713181626.39d398ea@skate> (raw)
In-Reply-To: <0Ln0qf-1R89A42Okf-00hKUN@mrelayeu.kundenserver.de>
Le Wed, 13 Jul 2011 18:10:33 +0200,
Wolfram Gloger <wg@malloc.de> a ?crit :
> Basically I copied the .mk from ffmpeg, but it isn't purely a
> s/FFmpeg/Libav/g job; the ffmpeg binary for example stays the same.
>
> I would prefer to keep the .mk's separate for this and two more
> reasons: the packages might well diverge and the duplication is not
> excessive IMHO.
Ok, fair enough.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-07-13 16:16 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
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 [this message]
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=20110713181626.39d398ea@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