[Buildroot] Some legal-info observations/problems

Ryan Barnett rjbarnet at rockwellcollins.com
Fri Oct 4 15:39:56 UTC 2013


Thomas Petazzoni <thomas.petazzoni at free-electrons.com> wrote on 
10/04/2013 10:34:52 AM:

> Dear Ryan Barnett,
> 
> On Fri, 4 Oct 2013 10:30:36 -0500, Ryan Barnett wrote:
> 
> > What if the license files are only available from a website?
> > 
> > For example, I'm looking to add a new package, tornado (python 
webserver)
> > to buildroot- http://www.tornadoweb.org/en/stable/ . However the 
license
> > isn't apart of the distribution itself but it points me to a website 
for
> > the license.
> > 
> > http://www.apache.org/licenses/LICENSE-2.0.html
> > 
> > Would we then put N/A for the license file? Or how do we want to 
handle 
> > this?
> > 
> > This is the second time in about a week that I've run into this well 
> > adding
> > a new package?
> > 
> > Eventually in my release process, I will have to go to that website 
and 
> > get
> > that license, be it Apache, or whatever license it may be and package 
that
> > up so supporting a URL method of getting a license would be nice.
> 
> My suggestion in this case would be to use <pkg>_LICENSE_FILES = N/A
> (or whatever magic value is chosen) and in parallel ask the upstream
> maintainer to include the license file directly into the release
> tarballs.

I'm fine with this approach, with having the magic value there it 
will help know that these are files that I manually need to go 
pull the licenses for.

I just thought I would through this situation I ran into today
out in this discussion since it is very applicable.

Thanks,
-Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131004/391a2f78/attachment-0002.html>


More information about the buildroot mailing list