From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] gupnp-tools: new package
Date: Sat, 30 Jul 2016 16:34:01 +0200 [thread overview]
Message-ID: <20160730163401.25d59138@free-electrons.com> (raw)
In-Reply-To: <1469778689-31893-2-git-send-email-fabrice.fontaine@orange.com>
Hello,
On Fri, 29 Jul 2016 09:51:29 +0200, Fabrice Fontaine wrote:
> GUPnP Tools are free replacements of Intel UPnP tools that use
> GUPnP. They provides client and server side tools which enable
> one to easily test and debug one's UPnP devices and control
> points.
>
> http://www.gupnp.org/
>
> Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com>
> ---
> package/Config.in | 1 +
> package/gupnp-tools/Config.in | 34 ++++++++++++++++++++++++++++++++++
> package/gupnp-tools/gupnp-tools.hash | 2 ++
> package/gupnp-tools/gupnp-tools.mk | 35 +++++++++++++++++++++++++++++++++++
> 4 files changed, 72 insertions(+)
> create mode 100644 package/gupnp-tools/Config.in
> create mode 100644 package/gupnp-tools/gupnp-tools.hash
> create mode 100644 package/gupnp-tools/gupnp-tools.mk
I've applied, after doing the following changes:
[Thomas:
- use "depends on BR2_PACKAGE_LIBGTK3" instead of a select, and
simplify the Config.in comments consequently.
- move from "Development tools" to "Networking applications"
- license is GPLv2+, not LGPLv2+.]
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-30 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 7:51 [Buildroot] [PATCH 1/2] gtksourceview: new package Fabrice Fontaine
2016-07-29 7:51 ` [Buildroot] [PATCH 2/2] gupnp-tools: " Fabrice Fontaine
2016-07-30 14:34 ` Thomas Petazzoni [this message]
2016-07-30 13:56 ` [Buildroot] [PATCH 1/2] gtksourceview: " 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=20160730163401.25d59138@free-electrons.com \
--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