From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new package: minidlna
Date: Tue, 5 Jul 2011 23:00:18 +0200 [thread overview]
Message-ID: <20110705230018.01be536a@skate> (raw)
In-Reply-To: <0MKxYi-1QcgdO2zs8-00018x@mrelayeu.kundenserver.de>
Hello Wolfram,
Le Fri, 01 Jul 2011 18:32:02 +0200,
Wolfram Gloger <wg@malloc.de> a ?crit :
> MiniDLNA is server software with the aim of being fully compliant with
> DLNA/UPnP-AV clients.
>
> This new package depends on libav (see my other patch) as I could not
> get it to work with the current ffmpeg package in buildroot.
>
> Signed-off-by: Wolfram Gloger <wg@malloc.de>
Could you sent your patch inline ?
Your .mk file lists multiple dependencies, but your Config.in forgets
to "depends on" or "select" them.
Your minidlna-1.0.20-cross.patch file must come with a header detailing
what the patch does and why it is needed, along with a Signed-off-by
line identifying the author of the patch. This patch uses STAGING_DIR
in several places, which makes the patch completely unsuitable for
upstream inclusion. Isn't there a way of making this a little bit more
generic so that there's at least a hope of getting this patch merged
upstream in the minidlna project ?
In the .mk file, remove all useless commented lines.
Also remove the
+ BR2_DEFAULT_KERNEL_HEADERS=$(BR2_DEFAULT_KERNEL_HEADERS) \
line, which apparently is useless.
Regarding the dependencies, is it directly minidlna that depends on
libvorbis, flac, libogg, etc. ? Or is it libav that depends on those ?
Regards,
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 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 16:32 [Buildroot] [PATCH] new package: minidlna Wolfram Gloger
2011-07-05 21:00 ` Thomas Petazzoni [this message]
2011-07-13 16:59 ` Wolfram Gloger
2011-07-13 17:09 ` 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=20110705230018.01be536a@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