mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Alm, Michael" <Michael.Alm@elac-wartsila.de>
To: "'ptxdist@pengutronix.de'" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] How to generate license report?
Date: Tue, 27 Mar 2018 09:26:38 +0000	[thread overview]
Message-ID: <241a5cf422bf4bdbad5c2c4b32cb881a@elac-wartsila.de> (raw)
In-Reply-To: <20180327074335.sm7nnxydkwgu6mp2@pengutronix.de>

Hi,

On Tue, Mar 27, 2018 at 09:43:35AM +0200, Michael Olbrich wrote:
> > > Is it possible to generate such a report? How?
> > 
> > This should probably be documented. You can get it via
> > 
> >    $ ptxdist make license-report
>
> That's currently the way to do this. It's not documented because I 
> actually want to hook this up somewhere. But I'm not sure where exactly.
>
> I want to move this stuff out of rules/post/ and do something similar to the image rules. 
> And then hook up these new packages these packages somewhere. I'm not sure 'world' 
> is the correct place, so a new command 'ptxdist license-report'?
> Any opinions on this?

Sounds ok for me. It might also be useful to only generate a license report including the target or 
host packages. In many cases only the target license report is of interest to the final customer.
So the command might look something like this:

'ptxdist license-report'   generates 2 reports: 1 for the target and 1 for the host packages
'ptxdist license-report target'   generates  1 report including the target packages only
'ptxdist license-report host'   generates  1 report including the host packages only

Also, it would be helpful to have a short-list with the package name, version and license 
type only, without all the license text. Maybe like this:

'ptxdist license-report target short'

foo, 1.0, BSD
bar, 2.8.1.5, GPLv2
...


Greets,
Michael


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2018-03-27  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22  9:51 Alexander Dahl
2018-03-22 10:09 ` [ptxdist] [PATCH] ptxdist: Add switch to generate PDF license report Denis OSTERLAND
2018-03-26  7:44 ` [ptxdist] How to generate license report? Roland Hieber
2018-03-26  7:54   ` [ptxdist] [PATCH] doc: ref parameter: document special make target 'license-report' Roland Hieber
2018-03-27  7:43   ` [ptxdist] How to generate license report? Michael Olbrich
2018-03-27  8:42     ` Alexander Dahl
2018-03-27  9:26     ` Alm, Michael [this message]
2018-03-28 20:31       ` Andreas Pretzsch
2018-03-29  7:31         ` Denis OSTERLAND

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=241a5cf422bf4bdbad5c2c4b32cb881a@elac-wartsila.de \
    --to=michael.alm@elac-wartsila.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