From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: LICENSE, LICENSE and LICENSE
Date: Sun, 17 Oct 2010 11:16:17 +0100 [thread overview]
Message-ID: <4CBACCF1.1020403@xora.org.uk> (raw)
In-Reply-To: <AANLkTikvPnJupAjwCps+3Zc73jVNyd7Mm-X1PP307a-D@mail.gmail.com>
On 16/10/2010 20:15, Frans Meulenbroeks wrote:
> Dear all,
>
> Being bored while waiting for a build to finish, I decided to to a
> grep for LICENSE on recipes/*/*
>
> As already reported on an earlier email about 375 recipes have no
> LICENSE (according to recipe_sanity).
>
> After a little bit of editing and sorting I came to the list at the
> end of this email.
> First digit is the number a license occurs, 2nd field is the license itself.
>
First thoughts in this is we need to standardise on names of licenses.
And for licenses that cannot be named like my personal favourite the
aspell-en recipe some way to indicate a "special" license and furthur
metadata about that license.
Graeme
next prev parent reply other threads:[~2010-10-17 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 19:15 LICENSE, LICENSE and LICENSE Frans Meulenbroeks
2010-10-17 2:56 ` Chris Larson
2010-10-17 10:16 ` Graeme Gregory [this message]
2010-10-20 19:25 ` Denys Dmytriyenko
2010-10-20 20:14 ` Frans Meulenbroeks
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=4CBACCF1.1020403@xora.org.uk \
--to=dp@xora.org.uk \
--cc=openembedded-devel@lists.openembedded.org \
/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