From: Roland Hieber <rohieb@rohieb.name>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] libmd: specification of license tags
Date: Tue, 4 Oct 2016 01:25:35 +0200 [thread overview]
Message-ID: <666fe6a8-421e-7aaf-2b5e-8bb23f0f2757@rohieb.name> (raw)
In-Reply-To: <1475525936.15532.48.camel@ws-apr.office.loc>
[-- Attachment #1.1.1: Type: text/plain, Size: 985 bytes --]
Hi,
> One option is of course to simply ignore it, i.e. not use it ;-)
I don't think this is a good option ;-)
> […]
> Now, as I have this can of worms open anyway, what would be the best way
> to specify a license tag ?
Apparently util-linux is similar to that, its README.licenses says:
> Please, check the source code for more details. A license is usually at the start
> of each source file.
The rules file simply specifies multiple licenses:
> UTIL_LINUX_NG_LICENSE := GPL-2.0, GPL-2.0+, GPL-3.0+, LGPL-2.0+, BSD-3-Clause, BSD-4-Clause, public_domain
> UTIL_LINUX_NG_LICENSE_FILES := \
> file://Documentation/licenses/COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> file://Documentation/licenses/COPYING.BSD-3;md5=58dcd8452651fc8b07d1f65ce07ca8af \
> file://Documentation/licenses/COPYING.UCB;md5=263860f8968d8bafa5392cab74285262 \
> file://Documentation/licenses/COPYING.LGPLv2.1;md5=4fbd65380cdd255951079008b364516c
- Roland
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-03 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 20:18 Andreas Pretzsch
2016-10-03 23:25 ` Roland Hieber [this message]
2016-10-04 14:26 ` Michael Olbrich
2016-10-04 16:19 ` Andreas Pretzsch
2016-10-04 14:19 ` Michael Olbrich
2016-10-04 16:12 ` Andreas Pretzsch
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=666fe6a8-421e-7aaf-2b5e-8bb23f0f2757@rohieb.name \
--to=rohieb@rohieb.name \
--cc=ptxdist@pengutronix.de \
/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