Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Konrad Weihmann <kweihmann@outlook.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH 1/2] ncurses: use COPYING file
Date: Wed, 13 Apr 2022 19:30:09 +0000	[thread overview]
Message-ID: <7c2d7899ef0a4d21993d2ac499d4bc5e@axis.com> (raw)
In-Reply-To: <HE1PR0902MB18019A87B3863FB6ABCC662AA8EC9@HE1PR0902MB1801.eurprd09.prod.outlook.com>

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Konrad Weihmann
> Sent: den 13 april 2022 19:09
> To: openembedded-core@lists.openembedded.org
> Cc: Konrad Weihmann <kweihmann@outlook.com>
> Subject: [OE-core] [PATCH 1/2] ncurses: use COPYING file
> 
> which has the same info as the in-file header used in before

That's not quite true. Please drop the last three lines of the COPYING 
file that contains editor configuration and a CVS $Id$.

Some of us use the output from LIC_FILES_CHKSUM to produce a combined 
license text for our products and any non-license related information 
that is included then becomes more or less problematic.

> 
> Signed-off-by: Konrad Weihmann <kweihmann@outlook.com>
> ---
>  meta/recipes-core/ncurses/ncurses.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-core/ncurses/ncurses.inc b/meta/recipes-
> core/ncurses/ncurses.inc
> index a0ecd8a80b..8d374a1522 100644
> --- a/meta/recipes-core/ncurses/ncurses.inc
> +++ b/meta/recipes-core/ncurses/ncurses.inc
> @@ -2,7 +2,7 @@ SUMMARY = "The New Curses library"
>  DESCRIPTION = "SVr4 and XSI-Curses compatible curses library and terminfo
> tools including tic, infocmp, captoinfo. Supports color, multiple
> highlights, forms-drawing characters, and automatic recognition of keypad
> and function-key sequences. Extensions include resizable windows and mouse
> support on both xterm and Linux console using the gpm library."
>  HOMEPAGE = "http://www.gnu.org/software/ncurses/ncurses.html"
>  LICENSE = "MIT"
> -LIC_FILES_CHKSUM =
> "file://ncurses/base/version.c;beginline=1;endline=27;md5=5526f2f3a29edc95
> 538b368a4771edda"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=f852913c5d988a5f5a2f1df7ba7ee893"
>  SECTION = "libs"
>  DEPENDS = "ncurses-native"
>  DEPENDS:class-native = ""
> --
> 2.25.1

//Peter



      reply	other threads:[~2022-04-14 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 17:08 [PATCH 1/2] ncurses: use COPYING file Konrad Weihmann
2022-04-13 19:30 ` Peter Kjellerstedt [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=7c2d7899ef0a4d21993d2ac499d4bc5e@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=kweihmann@outlook.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