From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 0/2] script to find package licenses
Date: Fri, 5 Aug 2016 09:53:53 +0200 [thread overview]
Message-ID: <20160805095353.68bf1fd9@free-electrons.com> (raw)
In-Reply-To: <57A44379.9010208@imgtec.com>
Hello,
On Fri, 5 Aug 2016 13:12:49 +0530, Rahul Bedarkar wrote:
> Intention of script is to help us to verify or correct legal info that
> we add in .mk file. This could be a handy tool that can be used by
> anyone when we do version bump or add new package. The complex tools
> that are available are generally used by upstream package providers for
> Open Source Compliance which provide lot more information than just file
> license. And integrating such tools in Buildroot might be difficult. But
> in Buildroot where we just need license of a package, script could be
> useful as a starting point.
I'm sorry, but I still don't see why we should merge a script that we
would have to maintain, while there are some existing, actively
developed and more powerful tools doing the same work.
Moreover, I believe that the cases that can be detected automatically
by a script (such as a clear GPL, LGPL, BSD or MIT license) are clearly
not the ones for which it is difficult to write the <pkg>_LICENSE
string.
The ones for which it is difficult are the ones that a script will
never handle as it can't recognize any pattern.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-05 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 14:16 [Buildroot] [RFC 0/2] script to find package licenses Rahul Bedarkar
2016-08-04 14:16 ` [Buildroot] [RFC 1/2] scripts: add a script to find licenses of package Rahul Bedarkar
2016-08-04 14:16 ` [Buildroot] [RFC 2/2] new make target <PKG>-find-licenses Rahul Bedarkar
2016-08-04 16:33 ` [Buildroot] [RFC 0/2] script to find package licenses Thomas Petazzoni
2016-08-05 2:03 ` Khem Raj
2016-08-05 7:42 ` Rahul Bedarkar
2016-08-05 7:53 ` Thomas Petazzoni [this message]
2016-08-08 17:42 ` Yann E. MORIN
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=20160805095353.68bf1fd9@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.