All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Nicolas Carrier <Nicolas.Carrier@orolia.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] package/lpeg: add missing LPEG_LICENSE_FILES
Date: Sat, 14 Jan 2023 22:00:46 +0100	[thread overview]
Message-ID: <20230114210046.GE199036@scaer> (raw)
In-Reply-To: <8ef2e2013a5e486034e602157d91b1de0d1ad374.camel@orolia.com>

Nicolas, All,

On 2023-01-13 13:44 +0000, Nicolas Carrier spake thusly:
> The lpeg.html file declares the licensing terms at its bottom, so it
> should work as a license file.

> From 12007e85d75daf941b8e82741e14ee1cb9c61893 Mon Sep 17 00:00:00 2001
> From: Nicolas Carrier <nicolas.carrier@orolia.com>
> Date: Fri, 13 Jan 2023 14:39:53 +0100
> Subject: [PATCH 1/1] package/lpeg: add missing LPEG_LICENSE_FILES
> 
> The lpeg.html file declares the licensing terms at its bottom, so it
> should work as a license file.
> 
> Signed-off-by: Nicolas Carrier <nicolas.carrier@orolia.com>
> ---
>  package/lpeg/lpeg.hash | 3 +++
>  package/lpeg/lpeg.mk   | 1 +
>  2 files changed, 4 insertions(+)
> 
> diff --git a/package/lpeg/lpeg.hash b/package/lpeg/lpeg.hash
> index 1ccaf242c4..f480ac6483 100644
> --- a/package/lpeg/lpeg.hash
> +++ b/package/lpeg/lpeg.hash
> @@ -1,2 +1,5 @@
>  # computed by luarocks/buildroot
>  sha256  e0d0d687897f06588558168eeb1902ac41a11edd1b58f1aa61b99d0ea0abbfbc  lpeg-1.0.2-1.src.rock
> +# computed locally
> +sha256  2b80a8cce793e008ba433e5e0184f20aca4a67ec741439fafd86a874a6a91c49  lpeg-1.0.2/lpeg.html
> +

    $ make check-package
    package/lpeg/lpeg.hash:5: empty line at end of file

> diff --git a/package/lpeg/lpeg.mk b/package/lpeg/lpeg.mk
> index cdb2e81a5f..82c733904b 100644
> --- a/package/lpeg/lpeg.mk
> +++ b/package/lpeg/lpeg.mk
> @@ -6,5 +6,6 @@
>  
>  LPEG_VERSION = 1.0.2-1
>  LPEG_LICENSE = MIT
> +LPEG_LICENSE_FILES = lpeg-1.0.2/lpeg.html

I've changed that to use $(LPEG_SUBDIR), which is autocomputed by the
luarosk-package infra to contain the proper package-version string.

Applied to master with that fixed, thanks.

Regards,
Yann E. MORIN.

>  
>  $(eval $(luarocks-package))
> -- 
> 2.30.2
> 

> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot


-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-01-14 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 13:44 [Buildroot] package/lpeg: add missing LPEG_LICENSE_FILES Nicolas Carrier
2023-01-14 21:00 ` Yann E. MORIN [this message]
2023-01-16 14:45 ` Peter Korsgaard

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=20230114210046.GE199036@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=Nicolas.Carrier@orolia.com \
    --cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.