Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/3] python-pbr: new package
Date: Wed, 25 Dec 2019 21:45:12 +0100	[thread overview]
Message-ID: <20191225214512.65d2aca4@windsurf> (raw)
In-Reply-To: <20191125193850.862709-1-aduskett@gmail.com>

On Mon, 25 Nov 2019 11:38:48 -0800
aduskett at gmail.com wrote:

> From: Adam Duskett <aduskett@greenlots.com>
> 
> PBR is a library that injects some useful and sensible default
> behaviors into a setuptools run.
> 
> Signed-off-by: Adam Duskett <aduskett@greenlots.com>

Applied, with one minor change.

> +PYTHON_PBR_VERSION = 5.4.3
> +PYTHON_PBR_SOURCE = pbr-$(PYTHON_PBR_VERSION).tar.gz
> +PYTHON_PBR_SITE = https://files.pythonhosted.org/packages/99/f1/7807d3409c79905a907f1c616d910c921b2a8e73c17b2969930318f44777
> +PYTHON_PBR_SETUP_TYPE = setuptools
> +PYTHON_PBR_LICENSE = BSD-3-Clause, Apache-2.0

Apache-2.0 is really the main license, BSD-3-Clause is only for the
test stuff, if I understood correctly. So I changed to:

PYTHON_PBR_LICENSE = Apache-2.0 (module), BSD-3-Clause (test package)

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2019-12-25 20:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 19:38 [Buildroot] [PATCH/next 1/3] python-pbr: new package aduskett at gmail.com
2019-11-25 19:38 ` [Buildroot] [PATCH/next 2/3] python-lockfile: " aduskett at gmail.com
2019-12-25 21:00   ` Thomas Petazzoni
2019-11-25 19:38 ` [Buildroot] [PATCH/next 3/3] package/python-daemon: select python-lockfile aduskett at gmail.com
2019-12-25 21:00   ` Thomas Petazzoni
2019-12-25 20:45 ` 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=20191225214512.65d2aca4@windsurf \
    --to=thomas.petazzoni@bootlin.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