From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why have legal info for host packages?
Date: Fri, 7 Jun 2013 11:51:00 +0200 [thread overview]
Message-ID: <20130607115100.510530ad@skate> (raw)
In-Reply-To: <20130602161923.GB3510@free.fr>
Dear Yann E. MORIN,
On Sun, 2 Jun 2013 18:19:23 +0200, Yann E. MORIN wrote:
> On 2013-06-02 12:12 -0400, Danomi Manchego spake thusly:
> > I was using the outputs from "make legal-info" yesterday as the basis for
> > our embedded product's licenses web page, and found myself modifying
> > pkg-generic.mk to exclude host packages from the legal info collection. So
> > I was wondering - what is the value in including the legal info of packages
> > built for the host?
>
> Some companies use Buildroot as a base for the SDK and provide pre-built
> environment to their customers. So, we have to also install legal-info
> for host packages to cope with this situation.
Yes, but as we discussed some time ago, the host packages should either
be identified as such in the legal info, or even maybe a separate
manifest.csv file should be generated for the host packages.
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:[~2013-06-07 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 16:12 [Buildroot] Why have legal info for host packages? Danomi Manchego
2013-06-02 16:19 ` Yann E. MORIN
2013-06-07 9:51 ` Thomas Petazzoni [this message]
2013-06-07 15:46 ` Yann E. MORIN
2013-06-07 16:23 ` 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=20130607115100.510530ad@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