mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Markus Niebel <list-09_ptxdist@tqsc.de>
To: ptxdist@pengutronix.de
Cc: m.olbrich@pengutronix.de, guille.rodriguez@gmail.com,
	Markus Niebel <Markus.Niebel@tq-group.com>
Subject: Re: [ptxdist] [RFC 0/2] add a way to extract license text from packages
Date: Fri, 30 Jan 2015 08:48:00 +0100	[thread overview]
Message-ID: <54CB3730.8040300@tqsc.de> (raw)
In-Reply-To: <CABDcavb6bRCuTNdKD+wF2TPtDdO=_m=1f6qE-+2+NorzFDNrEQ@mail.gmail.com>

Hello,
Am 29.01.2015 um 21:23 schrieb Guillermo Rodriguez Garcia:
> Hi,
> 
> If I understand correctly the auditing procedure before this patch would be:
> 
> 1. Collect all existing files in state/<pkg>.license
> 2. Each .license file contains the license name (e.g. "GPL") -- use
> this to find the actual license text
> 3. Audit each license
> 
> What would be the difference after this patch?
> 

My goal is to have a single place where the licenses of the target packages
are collected (think of it like export_src for license information - license
names and license text). 

Motivation:
- Some packages have additional clauses to the license text (Qt for instances). 
  So it would be a benefit to have the text from the package.
- If you deliver binaries of a BSP (preinstalled or for download) some licenses
  force you to supply the license text with the binary
- In some cases non developers need to look over the licenses
- AFAIK other build tools (yocto, buildroot) has similar features

Hope this helps

Markus

> Thanks,
> 
> Guillermo
> 
> 
> 2015-01-29 8:45 GMT+01:00 Markus Niebel <list-09@tqsc.de>:
>> Am 21.01.2015 um 09:12 schrieb Markus Niebel:
>>> From: Markus Niebel <Markus.Niebel@tq-group.com>
>>>
>>> just as an RFC: it would be good to have above said features to ease
>>> deployment and auditing.
>>>
>>> First patch implements this feature as an addon of the targetinstall
>>> stage. Second patch shows the feature for a package that uses it's own
>>> license
>>>
>>> TODO:
>>> maybe targetinstall is not the right place, just in case the license
>>> is altered during patching the package.
>>>
>>> Markus Niebel (2):
>>>   ptxdist: add license text extraction
>>>   icu: add LICENSE_TEXT
>>>
>>>  rules/icu.make                         |  5 +++--
>>>  rules/post/ptxd_make_world_common.make |  1 +
>>>  scripts/lib/ptxd_make_xpkg_common.sh   |  3 +++
>>>  scripts/lib/ptxd_make_xpkg_finish.sh   | 11 +++++++++++
>>>  4 files changed, 18 insertions(+), 2 deletions(-)
>>>
>> ping ...
>>
>> Any interest in this topic?
>>
>> Regards
>>
>> Markus
>>
>> --
>> ptxdist mailing list
>> ptxdist@pengutronix.de
> 
> 
> 


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-01-30  7:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  8:12 Markus Niebel
2015-01-21  8:12 ` [ptxdist] [RFC 1/2] ptxdist: add license text extraction Markus Niebel
2015-01-21  8:12 ` [ptxdist] [RFC 2/2] icu: add LICENSE_TEXT Markus Niebel
2015-01-29  7:45 ` [ptxdist] [RFC 0/2] add a way to extract license text from packages Markus Niebel
2015-01-29 20:23   ` Guillermo Rodriguez Garcia
2015-01-30  7:48     ` Markus Niebel [this message]
2015-02-10 13:14       ` Guillermo Rodriguez Garcia
2015-02-11 10:50       ` Hubert Feurstein
2015-02-11 11:19         ` Juergen Borleis
2015-02-11 13:02           ` Michael Olbrich
2015-02-17  8:10             ` Markus Niebel
2015-02-19 14:12               ` Michael Olbrich
2015-02-12  7:33           ` Markus Niebel
2015-02-12  8:55             ` Robert Schwebel
2016-10-03 22:23           ` [ptxdist] license-report: extend to generate textual list of package + licenses Andreas Pretzsch
2016-10-04 13:02             ` Michael Olbrich
2016-10-04 17:15               ` Andreas Pretzsch
2016-10-05 12:53                 ` Michael Olbrich

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=54CB3730.8040300@tqsc.de \
    --to=list-09_ptxdist@tqsc.de \
    --cc=Markus.Niebel@tq-group.com \
    --cc=guille.rodriguez@gmail.com \
    --cc=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