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] [PATCH] license-csv: Add rules to generate CSV license report.
Date: Thu, 29 Mar 2018 15:54:20 +0200	[thread overview]
Message-ID: <20180329135420.dm6m3taiobjhfayn@pengutronix.de> (raw)
In-Reply-To: <1522327576.5478.52.camel@diehl.com>

On Thu, Mar 29, 2018 at 12:46:16PM +0000, Denis OSTERLAND wrote:
> Am Donnerstag, den 29.03.2018, 14:08 +0200 schrieb Andreas Pretzsch:
> > On Do, 2018-03-29 at 07:29 +0000, Denis OSTERLAND wrote:
> > Extending the field list by section is a good point, thanks. Will do.
> > 
> > But I would refrain from including the URL (for now), simply as it will
> > include all sorts of characters, which then will require proper
> > escaping. And in 20+ years, I've seen way too many broken parsers (and
> > escapers)...
> > Beside, the key point of the CSV list (to me / customers) is to have a
> > diff'able list of included packages (which ones, version, license),
> > beside the full fledged report. To see if one needs to look into
> > something. So URL is nice, but not mandatory.
> > 
> > Last, about the CSV separator, I chose | out of experience, avoiding
> > most collisions. Both , and ; show up often in text and even version
> > tags. Yes, they are marked as string with "", but back to "broken
> > parsers"...
> > 
> > So I still tend to a CSV output like:
> > 
> > "name"|"version"|"section"|"licenses"|"flags"
> > "somepackage"|"1.2.3"|"osi-conform"|"Apache-2.0"|"attribution"
> > [...]
> > 
> > 
> > Denis, what do you think ?
> You are right, URL tend to be brittle.
> We use it as input for an overview page on embedded web server.
> This will need some refactoring.

You could overwrite the function that generates the per package file in
your BSP.

> By the way, is it possible depend on your csv report from make?
> I guess I will need to add some wrapper target to call sh function.

There is a make target for the license report. If necessary we can
restructure this as needed.

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:[~2018-03-29 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29  7:29 Denis OSTERLAND
2018-03-29  9:51 ` Michael Olbrich
2018-03-29 12:08 ` Andreas Pretzsch
2018-03-29 12:46   ` Denis OSTERLAND
2018-03-29 13:54     ` Michael Olbrich [this message]
2018-03-29 15:07     ` 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=20180329135420.dm6m3taiobjhfayn@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