From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: MIME-Version: 1.0 In-Reply-To: <54CB3730.8040300@tqsc.de> References: <1421827952-15513-1-git-send-email-list-09_ptxdist@tqsc.de> <54C9E505.1080408@tqsc.de> <54CB3730.8040300@tqsc.de> Date: Tue, 10 Feb 2015 14:14:38 +0100 Message-ID: From: Guillermo Rodriguez Garcia Subject: Re: [ptxdist] [RFC 0/2] add a way to extract license text from packages Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: "ptxdist@pengutronix.de" Cc: m.olbrich@pengutronix.de, Markus Niebel Hello Markus, I'm no expert at this topic but here is how I would handle this: 1. Collect all existing files in state/.license into a license list. Example: #!/bin/sh if [ $# -eq 0 -o ! -e $1/state ]; then echo "usage: $0 " exit 1 fi for file in $1/state/*.license ; do pkg=${file##*/} pkg=${pkg%%.*} echo "$pkg: `cat $file`" done 2. Build a tool that would go through this list and download/collect the actual license texts. i.e. very similar to what you already did, but outside of ptxdist. Then if this can be easily done "outside" of ptxdist (as a separate script) I guess that the real question is whether this is a desirable feature to have in ptxdist itself. But this is something for the ptxdist experts to decide :-) Guillermo 2015-01-30 8:48 GMT+01:00 Markus Niebel : > 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/.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 : >>> Am 21.01.2015 um 09:12 schrieb Markus Niebel: >>>> From: Markus Niebel >>>> >>>> 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 -- Guillermo Rodriguez Garcia guille.rodriguez@gmail.com -- ptxdist mailing list ptxdist@pengutronix.de