From: <niko.mauno@vaisala.com>
To: <leonardo.sandoval.gonzalez@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Allow overriding environment specific SPDX variables
Date: Wed, 3 May 2017 15:30:22 +0000 [thread overview]
Message-ID: <968159e5-5987-e42c-54e6-e2ac43d033dd@vaisala.com> (raw)
In-Reply-To: <1493824168.1761.12.camel@linux.intel.com>
On 03.05.2017 18:09, Leonardo Sandoval wrote:
> On Wed, 2017-05-03 at 10:39 +0000, niko.mauno@vaisala.com wrote:
>> Change certain variable assignments from 'hard' (=) to 'soft' (?=) so that
>> suitable permutations of values for these variables can be assigned eg. in
>> custom meta layers. Otherwise eg. fossology server is limited to run on same
>> machine as bitbake, and generated SPDX files are placed into home directory
>> path of a custom luser account.
>>
>> Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
>> ---
>> meta/conf/licenses.conf | 12 +++++++-----
>> 1 file changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/meta/conf/licenses.conf b/meta/conf/licenses.conf
>> index d210a0e..fcaec1b 100644
>> --- a/meta/conf/licenses.conf
>> +++ b/meta/conf/licenses.conf
>> @@ -123,7 +123,9 @@ SPDXLICENSEMAP[SGIv1] = "SGI-1"
>>
>> ## SPDX temporary directory
>> SPDX_TEMP_DIR = "${WORKDIR}/spdx_temp"
>> -SPDX_MANIFEST_DIR = "/home/yocto/fossology_scans"
>> +
>> +## Output directory for generated SPDX files
>> +SPDX_MANIFEST_DIR ?= "/home/yocto/fossology_scans"
>
> not sure if this is right, but shouldn't be SPDX_MANIFEST_DIR ?=
> "${SPDX_TEMP_DIR}/fossology_scans' so this way we do not rely on a
> yocto's home folder?
>
> Leo
>
That would seem like a more feasible default. Is this something that
should be addressed now in this patch, or in another (later) changeset?
>>
>> ## SPDX Format info
>> SPDX_VERSION = "SPDX-1.1"
>> @@ -142,7 +144,7 @@ DATA_LICENSE = "CC0-1.0"
>> # information.
>> #
>>
>> -FOSS_NO_COPYRIGHT = "true"
>> +FOSS_NO_COPYRIGHT ?= "true"
>>
>> # A option defined as[FOSS_RECURSIVE_UNPACK] in ./meta/conf/licenses.conf. is
>> # used to control if FOSSology server need recursively unpack tar.gz file which
>> @@ -156,7 +158,7 @@ FOSS_NO_COPYRIGHT = "true"
>> # FOSSology server recursively unpack components.
>> #
>>
>> -FOSS_RECURSIVE_UNPACK = "false"
>> +FOSS_RECURSIVE_UNPACK ?= "false"
>>
>> # An option defined as [FOSS_FULL_SPDX] in ./meta/conf/licenses.conf is used to
>> # control what kind of SPDX output to get from the FOSSology server.
>> @@ -171,7 +173,7 @@ FOSS_RECURSIVE_UNPACK = "false"
>> # license tags in the report will be "NOASSERTION"
>> #
>>
>> -FOSS_FULL_SPDX = "true"
>> +FOSS_FULL_SPDX ?= "true"
>>
>> # FOSSologySPDX instance server. http://localhost/repo is the default
>> # installation location for FOSSology.
>> @@ -180,7 +182,7 @@ FOSS_FULL_SPDX = "true"
>> # https://github.com/spdx-tools/fossology-spdx/wiki/Fossology-SPDX-Web-API
>> #
>>
>> -FOSS_BASE_URL = "http://localhost/repo/?mod=spdx_license_once"
>> +FOSS_BASE_URL ?= "http://localhost/repo/?mod=spdx_license_once"
>> FOSS_SERVER = "${FOSS_BASE_URL}&fullSPDXFlag=${FOSS_FULL_SPDX}&noCopyright=${FOSS_NO_COPYRIGHT}&recursiveUnpack=${FOSS_RECURSIVE_UNPACK}"
>>
>> FOSS_WGET_FLAGS = "-qO - --no-check-certificate --timeout=0"
>> --
>> 2.1.4
>
>
next prev parent reply other threads:[~2017-05-03 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 10:39 [PATCH] Allow overriding environment specific SPDX variables niko.mauno
2017-05-03 11:01 ` ✗ patchtest: failure for " Patchwork
2017-05-03 15:09 ` [PATCH] " Leonardo Sandoval
2017-05-03 15:30 ` niko.mauno [this message]
2017-05-03 15:42 ` Leonardo Sandoval
2017-05-05 11:30 ` niko.mauno
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=968159e5-5987-e42c-54e6-e2ac43d033dd@vaisala.com \
--to=niko.mauno@vaisala.com \
--cc=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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