From: Erwin Rol <mailinglists@erwinrol.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] license info
Date: Wed, 11 Feb 2015 17:28:45 +0100 [thread overview]
Message-ID: <54DB833D.8050604@erwinrol.com> (raw)
In-Reply-To: <CABDcavYZx_Oj8pZqWS6jPK-eWd5KfSQ87s0btE33tXL5Wr4tfA@mail.gmail.com>
The target is the "software", by having the license files on the target
the "software" can reproduce the license files when asked (telnet/ssh +
cat license.txt)
- Erwin
On 11-2-2015 17:11, Guillermo Rodriguez Garcia wrote:
> In many cases the actual requirement is that the licensing information
> is shown in the software itself (e.g. if it has a GUI) or in the
> accompanying documentation (e.g. user manuals and such). None of this
> would happen automatically if the licenses are just copied to the
> target rootfs, so I guess that this would not be very useful in
> itself.
>
> Guillermo
>
> 2015-02-11 16:52 GMT+01:00 Erwin Rol <mailinglists@erwinrol.com>:
>> Hey all,
>>
>> I see Michael is busy adding license info, which is a good thing. But
>> AFAIK (but IANAL) the license info should also be available on the
>> target. Does the new ptxdist also install the license files onto the
>> target (root)fs ?
>>
>> - Erwin
>>
>> --
>> ptxdist mailing list
>> ptxdist@pengutronix.de
>
>
>
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-02-11 16:28 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 [this message]
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
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=54DB833D.8050604@erwinrol.com \
--to=mailinglists@erwinrol.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