Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Why have legal info for host packages?
Date: Fri, 7 Jun 2013 17:46:49 +0200	[thread overview]
Message-ID: <20130607154649.GA6124@free.fr> (raw)
In-Reply-To: <20130607115100.510530ad@skate>

Thomas, All,

On 2013-06-07 11:51 +0200, Thomas Petazzoni spake thusly:
> 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.

Indeed. I never said otherwise. I was just pointing out that we also
want to generate it for host packages, and was giving an example why
this was needed.

That this legal-info stuff be generated in a separate location (file,
dir) is orthogonal: we want it generated.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-06-07 15:46 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
2013-06-07 15:46     ` Yann E. MORIN [this message]
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=20130607154649.GA6124@free.fr \
    --to=yann.morin.1998@free.fr \
    --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