From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] How to generate license report?
Date: Wed, 28 Mar 2018 22:31:15 +0200 [thread overview]
Message-ID: <1522269075.24606.5.camel@ws-apr.office.loc> (raw)
In-Reply-To: <241a5cf422bf4bdbad5c2c4b32cb881a@elac-wartsila.de>
On Di, 2018-03-27 at 09:26 +0000, Alm, Michael wrote:
> 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
> ...
Have a look at my patchset "license-report: also create CSV lists" just
sent to the list. It adds CSV generation to the regular process
(triggered by "ptxdist make license-report").
It might already solve your task.
Best regards,
Andreas
--
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:[~2018-03-28 20:31 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
2018-03-28 20:31 ` Andreas Pretzsch [this message]
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=1522269075.24606.5.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