From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Why have legal info for host packages?
Date: Sun, 2 Jun 2013 18:19:23 +0200 [thread overview]
Message-ID: <20130602161923.GB3510@free.fr> (raw)
In-Reply-To: <CANxTyt6LO-Q3orQnXGL873wG5z9f3ufiE6YOUNMuBq--8VMzFQ@mail.gmail.com>
Danomi, All,
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.
That'a at least one reason. There are maybe others.
Note: I initially thought like you, but in the end was converted to
accept and expect the current situation! ;-)
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-06-02 16:19 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 [this message]
2013-06-07 9:51 ` Thomas Petazzoni
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=20130602161923.GB3510@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