[Buildroot] Why have legal info for host packages?

[Buildroot] Why have legal info for host packages?

[Danomi Manchego]

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?

Danomi -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130602/e9662ccb/attachment.html>

[Buildroot] Why have legal info for host packages?

[Yann E. MORIN]

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.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] Why have legal info for host packages?

[Thomas Petazzoni]

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

[Buildroot] Why have legal info for host packages?

[Yann E. MORIN]

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.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] Why have legal info for host packages?

[Thomas Petazzoni]

Dear Yann E. MORIN,

On Fri, 7 Jun 2013 17:46:49 +0200, Yann E. MORIN wrote:

> > 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.

Agreed. But the way your e-mail was written could be understood as "the
way things are currently is correct, we don't want to change it", which
is why I reacted to it.

But anyway, I know we both agree :)

Thanks,

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