mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] license-report: extend to generate textual list of package + licenses
Date: Tue, 4 Oct 2016 15:02:40 +0200	[thread overview]
Message-ID: <20161004130240.ehjvz3qe2t3v7h4y@pengutronix.de> (raw)
In-Reply-To: <1475533380.15532.87.camel@ws-apr.office.loc>

Hi,

On Tue, Oct 04, 2016 at 12:23:00AM +0200, Andreas Pretzsch wrote:
> On Mi, 2015-02-11 at 12:19 +0100, Juergen Borleis 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.
> 
> First, this one is wonderful, and works like a charm. Thanks a lot.
> 
> What I am missing is an overview.
> Mainly as an external list, but maybe also in the reports.
> 
> I'm talking about e.g. a simple CSV, listing all the included packages,
> like in "pkgname | pkgversion | licenses". So something like
> [...]
> busybox|1.24.2|GPL-2.0
> [...]
> Sensible escaping would be something to look at, but anyway.
> 
> Point is, this list would be easily diff'able between releases.
> And lawyers tend to be more expensive than developers...
> 
> Also, one can sort it and make matrices of any kind, e.g. sort by GPLv3,
> and so on.
> 
> Above would be the minimum information, for anything else, one can look
> into the big report. Maybe the flags like "attribution" and "choice"
> would be interessting, too.
> 
> Now, this can be done with some shell scripting, outside of the build
> process.
> But as there is already the license-report generation, this would be the
> perfect place for it.
> 
> Has anyone already (partly) implemented this ?
> Would be happy to pick up the pieces and also mainline it. Just asking,
> before I start hacking things twice...

I don't think there are any implementations like this.

If we do something like this, then I'd like to take this a step further. I
think there are more use-cases for data like this. And there a probably
conflicting requirements for the different files and output formats.

The main issue with PTXdist is that we cannot just iterate over all
packages is one script. So what I'd like to see is something like the
current report stage to aggregate all possibly interesting data about the
packages and later convert an filter that into the required output.
What would be a good intermediate format for this? I'd like to avoid
escaping problems if possible.

Michael

-- 
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

  reply	other threads:[~2016-10-04 13:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  8:12 [ptxdist] [RFC 0/2] add a way to extract license text from packages 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
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 [this message]
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=20161004130240.ehjvz3qe2t3v7h4y@pengutronix.de \
    --to=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