Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-oe][PATCH 01/12] nbench-byte: Fix license QA error
Date: Fri, 26 Dec 2014 11:26:02 -0800	[thread overview]
Message-ID: <549DB64A.5060904@gmail.com> (raw)
In-Reply-To: <1419621700-1102-1-git-send-email-otavio@ossystems.com.br>

Otavio,
Thanks.

I just saw this this morning.

- armin

On 12/26/2014 11:21 AM, Otavio Salvador wrote:
> The license is not a common only and seems to be a 'free distribution'
> license but without explicit rules about modification or similar. Due
> that, we copied the license text from the README file and added it
> onto nbench-byte license file.
>
> This fixes following QA error:
>
> ,----
> | WARNING: Recipe nbench-byte, LICENSE (freely distributable) has
> |     invalid format, LICENSES must have operator "([&|() ])" between
> | 	them.
> `----
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>   meta-oe/licenses/nbench-byte                               | 10 ++++++++++
>   meta-oe/recipes-benchmark/nbench-byte/nbench-byte_2.2.3.bb |  2 +-
>   2 files changed, 11 insertions(+), 1 deletion(-)
>   create mode 100644 meta-oe/licenses/nbench-byte
>
> diff --git a/meta-oe/licenses/nbench-byte b/meta-oe/licenses/nbench-byte
> new file mode 100644
> index 0000000..7e47ba6
> --- /dev/null
> +++ b/meta-oe/licenses/nbench-byte
> @@ -0,0 +1,10 @@
> +THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
> +IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
> +OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
> +IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
> +INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
> +NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> +DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
> +THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
> +THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> diff --git a/meta-oe/recipes-benchmark/nbench-byte/nbench-byte_2.2.3.bb b/meta-oe/recipes-benchmark/nbench-byte/nbench-byte_2.2.3.bb
> index a98d507..2eedd7e 100644
> --- a/meta-oe/recipes-benchmark/nbench-byte/nbench-byte_2.2.3.bb
> +++ b/meta-oe/recipes-benchmark/nbench-byte/nbench-byte_2.2.3.bb
> @@ -2,7 +2,7 @@ DESCRIPTION = "BYTE Magazine's native benchmarks (also called BYTEmark) \
>   designed to expose the capabilities of a system's CPU, FPU, \
>   and memory system."
>   HOMEPAGE = "http://www.tux.org/~mayer/linux/"
> -LICENSE = "freely distributable"
> +LICENSE = "nbench-byte"
>   LIC_FILES_CHKSUM = "file://README;beginline=57;endline=66;md5=020ef579f8fa5746b7e307a54707834f"
>   SECTION = "console/utils"
>
>


      parent reply	other threads:[~2014-12-26 19:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 19:21 [meta-oe][PATCH 01/12] nbench-byte: Fix license QA error Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 02/12] dash: Fix license format " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 03/12] sound-theme-freedesktop: " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 04/12] soft66: " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 05/12] log4cplus: " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 06/12] libutempter: " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 07/12] libftdi: " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 08/12] procmail: " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 09/12] libspatialite: " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 10/12] ttf-sazanami: " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 11/12] navit: " Otavio Salvador
2014-12-26 19:21 ` [meta-oe][PATCH 12/12] t1lib: " Otavio Salvador
2014-12-26 19:26 ` akuster808 [this message]

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=549DB64A.5060904@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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