From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: m.olbrich@pengutronix.de, guille.rodriguez@gmail.com,
Markus Niebel <Markus.Niebel@tq-group.com>
Subject: Re: [ptxdist] [RFC 0/2] add a way to extract license text from packages
Date: Thu, 12 Feb 2015 09:55:32 +0100 [thread overview]
Message-ID: <20150212085532.GO15673@pengutronix.de> (raw)
In-Reply-To: <54DC574C.1040908@tqsc.de>
Hi,
On Thu, Feb 12, 2015 at 08:33:32AM +0100, Markus Niebel wrote:
> > On Wednesday 11 February 2015 11:50:16 Hubert Feurstein wrote:
> >> IMHO the proposal by Markus makes sense. I have had the same issues
> >> with collecting license texts in the past. So a solution integrated in
> >> PTXdist would be great. Because then it would be possible to collect
> >> the license texts depending on the config options of a package
> >> (sometimes plugins have a different license).
> >
> > Please checkout current PTXdist master and run "ptxdist make license-report"
> > inside a PTXdist project. You need "LATEX" and "dot" to make it work.
>
> Sounds great, will try it. Thanks
Please do so - it's a good opportunity to share forces here. The whole
license compliance topic is gaining speed recently.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-02-12 8:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 8:12 Markus Niebel
2015-01-21 8:12 ` [ptxdist] [RFC 1/2] ptxdist: add license text extraction Markus Niebel
2015-01-21 8:12 ` [ptxdist] [RFC 2/2] icu: add LICENSE_TEXT Markus Niebel
2015-01-29 7:45 ` [ptxdist] [RFC 0/2] add a way to extract license text from packages Markus Niebel
2015-01-29 20:23 ` Guillermo Rodriguez Garcia
2015-01-30 7:48 ` Markus Niebel
2015-02-10 13:14 ` Guillermo Rodriguez Garcia
2015-02-11 10:50 ` Hubert Feurstein
2015-02-11 11:19 ` Juergen Borleis
2015-02-11 13:02 ` Michael Olbrich
2015-02-17 8:10 ` Markus Niebel
2015-02-19 14:12 ` Michael Olbrich
2015-02-12 7:33 ` Markus Niebel
2015-02-12 8:55 ` Robert Schwebel [this message]
2016-10-03 22:23 ` [ptxdist] license-report: extend to generate textual list of package + licenses Andreas Pretzsch
2016-10-04 13:02 ` Michael Olbrich
2016-10-04 17:15 ` Andreas Pretzsch
2016-10-05 12:53 ` Michael Olbrich
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=20150212085532.GO15673@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=Markus.Niebel@tq-group.com \
--cc=guille.rodriguez@gmail.com \
--cc=m.olbrich@pengutronix.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