All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: buildroot@busybox.net
Subject: [Buildroot] Standardizing format for specifying license(s)
Date: Fri, 15 Jan 2016 14:12:47 +0100	[thread overview]
Message-ID: <1a9e07dbd834ef9ca57e1b6a91d043c2@localhost> (raw)
In-Reply-To: <5698DDBE.3000402@imgtec.com>

Hei hei, 

Am 2016-01-15 12:53, schrieb Rahul Bedarkar:
> Any suggestions and thoughts are welcome.

If not already done, I would suggest to have those license stuff
compatible with SPDX [1]. I noticed license names in at least some
packages are not the same as the identifiers on
https://spdx.org/licenses/ ? so if someone wants to generate SPDX stuff
from a buildroot project, it maybe would be better to have a format for
names and delimiters which make it easier towards SPDX package data.

Greets
Alex

[1] https://en.wikipedia.org/wiki/Software_Package_Data_Exchange

-- 
?With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.? (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

  reply	other threads:[~2016-01-15 13:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 11:53 [Buildroot] Standardizing format for specifying license(s) Rahul Bedarkar
2016-01-15 13:12 ` Alexander Dahl [this message]
2016-01-15 13:51   ` Thomas Petazzoni
2016-01-15 17:53     ` Luca Ceresoli
2016-01-16  1:02     ` Arnout Vandecappelle
2016-01-15 13:44 ` Thomas Petazzoni
2016-01-15 14:30   ` Rahul Bedarkar
2016-01-15 14:31     ` 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=1a9e07dbd834ef9ca57e1b6a91d043c2@localhost \
    --to=post@lespocky.de \
    --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.