From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] license-csv: Add rules to generate CSV license report.
Date: Thu, 29 Mar 2018 17:07:31 +0200 [thread overview]
Message-ID: <1522336051.9987.21.camel@ws-apr.office.loc> (raw)
In-Reply-To: <1522327576.5478.52.camel@diehl.com>
On Do, 2018-03-29 at 12:46 +0000, Denis OSTERLAND wrote:
> > 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.
> > [...]
> >
> > 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.
Hmmmm... Based on research and quite some debates with lawyers, I'd say
to have "only" the URL in a package list is critical at least.
For a solid conformance with the various FOSS licenses, you should
include most (if not all) of the content of the ptxdist license report.
The one from "license-compliance-distribution" would be enough, but I'd
suggest just to include the complete one.
My suggestion here would be to omit the URL in the overview page, and
also link to the license-blah.pdf (on the embedded webserver). Given you
have the storage space available.
So you provide everything in the device, and need no special hacks.
Of course, you could always add a (modified) version of
scripts/lib/ptxd_make_license_report.sh
scripts/lib/ptxd_make_world_license.sh
to your BSP folder under "scripts/lib/". Those will override the ones
from "official" PTXdist.
> 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.
About adding a wrapper called from make, see
"rules/post/ptxd_make_license_report.make".
Maybe as an additional step to "license-compliance-distribution".
Having something special for CSV, well, I just included it in the normal
flow, beside the TeX/PDF generation. Would say, that's a good place.
Of course, some hook to generate such a page would be nice, too.
But this is something Michael has to decide, mainly from a conceptual
point of view.
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
prev parent reply other threads:[~2018-03-29 15:07 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
2018-03-29 15:07 ` Andreas Pretzsch [this message]
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=1522336051.9987.21.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