From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] libmd: specification of license tags
Date: Tue, 04 Oct 2016 18:19:21 +0200 [thread overview]
Message-ID: <1475597961.7146.13.camel@ws-apr.office.loc> (raw)
In-Reply-To: <20161004142649.riu3qdcdexgamvcv@pengutronix.de>
On Di, 2016-10-04 at 16:26 +0200, Michael Olbrich wrote:
> > > Now, as I have this can of worms open anyway, what would be the best way
> > > to specify a license tag ?
> >
> Btw, if the license text ist only part of the file then you can use
> startline/endline to 'cut' it, see e.g. rules/e2fsprogs.make.
Noted also yesterday night. Good thing, congrats!
And it's even in the docs.
For those who follow this thread, quoted from "doc/ref_manual.rst":
``<PKG>_LICENSE``
The license of the package. The SPDX license identifiers should be used
here. Use ``proprietary`` for proprietary packages and ``ignore`` for
packages without their own license, e.g. meta packages or packages that
only install files from projectroot/.
``<PKG>_LICENSE_FILES``
A space separated list of URLs of license text files. The URLs must be
``file://`` URLs relative to ``<PKG>_DIR``. Absolute URLs using
``$(PTXDIST_WORKSPACE)`` can be used in case the license text is missing
in the upstream archive. Arguments are appended with ';' as separator.
The ``md5=<md5sum>`` argument is mandatory. It defines the md5 checksum
of the full license text. ``startline=<number>;endline=<number>`` can be
used in case the specified file contains more than just the license text,
e.g. if the license is in the header of a source file. For non ASCII or
UTF-8 files the encoding can be specified with ``encoding=<enc>``.
--
carpe noctem engineering
Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch
Dipl.-Ing. (FH) Andreas Pretzsch Tel. +49-(0)7307-936088-1
Lange Strasse 28a Fax: +49-(0)7307-936088-9
89250 Senden, Germany email: apr@cn-eng.de
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-04 16:19 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
2016-10-04 14:26 ` Michael Olbrich
2016-10-04 16:19 ` Andreas Pretzsch [this message]
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=1475597961.7146.13.camel@ws-apr.office.loc \
--to=apr@cn-eng.de \
--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