From: Bruno Thomsen <bth@kamstrup.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] license info
Date: Thu, 12 Feb 2015 08:48:38 +0000 [thread overview]
Message-ID: <915054555B5659448ACF8A70E114824D01984C17FC@Exchange2010.kamstrup.dk> (raw)
In-Reply-To: <CABDcavYYW=00Z_fb9X0Y3f9ts_4qUKL2Nmm=9A8a4JityGP-gA@mail.gmail.com>
> -----Original Message-----
> From: ptxdist-bounces@pengutronix.de [mailto:ptxdist-bounces@pengutronix.de] On Behalf Of Guillermo Rodriguez Garcia
> Sent: 11. februar 2015 18:12
> To: ptxdist@pengutronix.de
> Subject: Re: [ptxdist] license info
>
> OK. My view is that this (storing the license text in the rootfs) would be unnecessary for many licenses, while not completely fulfilling requirements for others. But IANAL either and you may very well be right :-)
We include all licenses with full text on rootfs using a custom Python script that generate a PHP page, so they can be shown by the embedded webserver.
Header -> Pre -> Package -> Post -> Pre -> Package -> Post -> ..... -> Footer
Package = name, version, license
/Bruno
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-02-12 8:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 15:52 Erwin Rol
2015-02-11 16:11 ` Guillermo Rodriguez Garcia
2015-02-11 16:28 ` Erwin Rol
2015-02-11 16:49 ` Guillermo Rodriguez Garcia
2015-02-11 17:03 ` Erwin Rol
2015-02-11 17:11 ` Guillermo Rodriguez Garcia
2015-02-12 8:48 ` Bruno Thomsen [this message]
2015-02-12 8:57 ` Robert Schwebel
2015-02-12 9:06 ` Bruno Thomsen
2015-02-12 9:26 ` Tim Sander
2015-02-12 9:36 ` Robert Schwebel
2015-02-11 16:41 ` Uwe Kleine-König
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=915054555B5659448ACF8A70E114824D01984C17FC@Exchange2010.kamstrup.dk \
--to=bth@kamstrup.com \
--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