All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] package/mtools: new host-package
Date: Sun, 10 Mar 2013 12:49:44 +0100	[thread overview]
Message-ID: <20130310124944.261867c4@skate> (raw)
In-Reply-To: <296699691239a90d5118c5cbe72f1ff57b3761a5.1362693294.git.yann.morin.1998@free.fr>

Yann, Luca,

Cc'ing Luca, there is a licensing infrastructure question below.

On Thu,  7 Mar 2013 22:55:31 +0100, Yann E. MORIN wrote:

> +MTOOLS_VERSION  = 4.0.18
> +MTOOLS_SOURCE   = mtools-$(MTOOLS_VERSION).tar.bz2
> +MTOOLS_SITE     = $(BR2_GNU_MIRROR)/mtools/

MTOOLS_LICENSE = GPLv3+
MTOOLS_LICENSE_FILES = COPYING

However, this makes me realize that we don't distinguish host packages
from target packages in the manifest.csv file. For example, once I had
the licensing informations for this mtools file, I have the following
line in my manifest.csv:

"mtools","4.0.18","GPLv3+","COPYING","mtools-4.0.18.tar.bz2"

And then, someone might think "damn, I have some GPLv3 software in my
system, I now need to comply with the additional special requirements
of GPLv3", while in fact it's not the case (as far as I know) because
mtools is not distributed on the embedded device. Maybe we need to
explicit which packages are on the target, which packages are on the
host, and which packages are on both, no?

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-03-10 11:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 21:55 [Buildroot] [pull request v4] Pull request for branch yem-host-image-tools Yann E. MORIN
2013-03-07 21:55 ` [Buildroot] [PATCH 1/6] package/e2fsprogs: add host-package selection Yann E. MORIN
2013-03-07 21:55 ` [Buildroot] [PATCH 2/6] package/dosfstools: " Yann E. MORIN
2013-03-07 21:55 ` [Buildroot] [PATCH 3/6] package/libconfuse: add host variant Yann E. MORIN
2013-03-07 21:55 ` [Buildroot] [PATCH 4/6] package/genimage: new host-only package Yann E. MORIN
2013-03-10 11:41   ` Thomas Petazzoni
2013-03-10 23:39     ` Yann E. MORIN
2013-03-11 21:30       ` Thomas Petazzoni
2013-03-07 21:55 ` [Buildroot] [PATCH 5/6] package/genpart: " Yann E. MORIN
2013-03-10 11:44   ` Thomas Petazzoni
2013-03-10 23:50     ` Yann E. MORIN
2013-03-07 21:55 ` [Buildroot] [PATCH 6/6] package/mtools: new host-package Yann E. MORIN
2013-03-10 11:49   ` Thomas Petazzoni [this message]
2013-03-11  0:02     ` Yann E. MORIN
2013-03-11 21:30       ` Thomas Petazzoni
2013-03-12 17:16       ` Luca Ceresoli
2013-03-12 17:40         ` Thomas De Schampheleire
2013-03-12 23:24           ` Arnout Vandecappelle
2013-03-15 11:48             ` Thomas Petazzoni
2013-03-10 11:40 ` [Buildroot] [pull request v4] Pull request for branch yem-host-image-tools Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2013-03-17 18:19 [Buildroot] [pull request v5] " Yann E. MORIN
2013-03-17 18:19 ` [Buildroot] [PATCH 6/6] package/mtools: new host-package Yann E. MORIN
2013-03-18 22:14   ` Peter Korsgaard
2013-02-17 23:04 [Buildroot] [pull request v3 'next'] Pull request for branch yem-host-image-tools Yann E. MORIN
2013-02-17 23:04 ` [Buildroot] [PATCH 6/6] package/mtools: new host-package Yann E. MORIN
2013-02-08 21:56 [Buildroot] [pull request v2] Pull request for branch yem-host-image-tools Yann E. MORIN
2013-02-08 21:56 ` [Buildroot] [PATCH 6/6] package/mtools: new host-package Yann E. MORIN
2013-02-08 17:32 [Buildroot] [pull request] Pull request for branch yem-host-image-tools Yann E. MORIN
2013-02-08 17:33 ` [Buildroot] [PATCH 6/6] package/mtools: new host-package Yann E. MORIN
2013-02-08 17:44   ` 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=20130310124944.261867c4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.