From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] python-docutils: new package
Date: Wed, 21 Sep 2016 20:51:17 +0200 [thread overview]
Message-ID: <20160921205117.2e8c2002@free-electrons.com> (raw)
In-Reply-To: <20160921134044.29040-1-yegorslists@googlemail.com>
Hello,
On Wed, 21 Sep 2016 15:40:43 +0200, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Host variant is needed for building python-daemon package.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> package/Config.in | 1 +
> package/python-docutils/Config.in | 9 +++++++++
> package/python-docutils/python-docutils.hash | 3 +++
> package/python-docutils/python-docutils.mk | 15 +++++++++++++++
> 4 files changed, 28 insertions(+)
> create mode 100644 package/python-docutils/Config.in
> create mode 100644 package/python-docutils/python-docutils.hash
> create mode 100644 package/python-docutils/python-docutils.mk
I slightly tweaked the description of the licenses, and then applied.
And indeed, this package is quite complicated in terms of licenses... I
hope what I've added is good enough. Hopefully other Buildroot
developers can have a look and suggest better descriptions if needed.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-09-21 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 13:40 [Buildroot] [PATCH 1/2] python-docutils: new package yegorslists at googlemail.com
2016-09-21 13:40 ` [Buildroot] [PATCH 2/2] python-daemon: add missing dependencies yegorslists at googlemail.com
2016-09-21 18:52 ` Thomas Petazzoni
2016-09-21 13:42 ` [Buildroot] [PATCH 1/2] python-docutils: new package Yegor Yefremov
2016-09-21 18:51 ` 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=20160921205117.2e8c2002@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