From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Pierre-Jean Texier <texier.pj2@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/numactl: use official license files
Date: Sun, 30 Oct 2022 17:28:23 +0100 [thread overview]
Message-ID: <20221030162823.GO1058960@scaer> (raw)
In-Reply-To: <20221029084455.97704-1-fontaine.fabrice@gmail.com>
Fabrice, All,
On 2022-10-29 10:44 +0200, Fabrice Fontaine spake thusly:
> Use official license files available since version 2.0.13 and
> https://github.com/numactl/numactl/commit/b4d36f6a34b045a67ed5c0314ec26f5514f4ee44
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/numactl/numactl.hash | 3 ++-
> package/numactl/numactl.mk | 2 +-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/package/numactl/numactl.hash b/package/numactl/numactl.hash
> index 802175d360..a261eab9d0 100644
> --- a/package/numactl/numactl.hash
> +++ b/package/numactl/numactl.hash
> @@ -1,3 +1,4 @@
> # Locally calculated
> sha256 1ee27abd07ff6ba140aaf9bc6379b37825e54496e01d6f7343330cf1a4487035 numactl-2.0.14.tar.gz
> -sha256 e2b738b1303c088421b09933a78c1326fe43692e2c05a7c510a2eb7e7a8eb575 README.md
> +sha256 ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6 LICENSE.GPL2
> +sha256 dc626520dcd53a22f727af3ee42c770e56c97a64fe3adb063799d8ab032fe551 LICENSE.LGPL2.1
> diff --git a/package/numactl/numactl.mk b/package/numactl/numactl.mk
> index cf9c759693..6ff94091e9 100644
> --- a/package/numactl/numactl.mk
> +++ b/package/numactl/numactl.mk
> @@ -7,7 +7,7 @@
> NUMACTL_VERSION = 2.0.14
> NUMACTL_SITE = $(call github,numactl,numactl,v$(NUMACTL_VERSION))
> NUMACTL_LICENSE = LGPL-2.1 (libnuma), GPL-2.0 (programs)
> -NUMACTL_LICENSE_FILES = README.md
> +NUMACTL_LICENSE_FILES = LICENSE.GPL2 LICENSE.LGPL2.1
> NUMACTL_INSTALL_STAGING = YES
> NUMACTL_AUTORECONF = YES
> NUMACTL_CONF_ENV = CFLAGS="$(TARGET_CFLAGS) -fPIC"
> --
> 2.35.1
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2022-10-30 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 8:44 [Buildroot] [PATCH 1/2] package/numactl: use official license files Fabrice Fontaine
2022-10-29 8:44 ` [Buildroot] [PATCH 2/2] package/numactl: bump to version 2.0.16 Fabrice Fontaine
2022-10-30 16:28 ` Yann E. MORIN
2022-10-30 16:28 ` Yann E. MORIN [this message]
2022-11-13 14:26 ` [Buildroot] [PATCH 1/2] package/numactl: use official license files 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=20221030162823.GO1058960@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=texier.pj2@gmail.com \
/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