public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yash.Shinde@windriver.com, openembedded-core@lists.openembedded.org
Cc: Randy.MacLeod@windriver.com, Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH v2 2/3] rust: Upgrade 1.84.1->1.85.0
Date: Mon, 31 Mar 2025 07:24:48 +0100	[thread overview]
Message-ID: <6a0be636d9c44b3166ac50e42c34aedf13a1be28.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250331055424.1978243-2-Yash.Shinde@windriver.com>

On Sun, 2025-03-30 at 22:54 -0700, Yash Shinde via
lists.openembedded.org wrote:
> From: Yash Shinde <Yash.Shinde@windriver.com>
> 
> Rust stable version updated to 1.85.0
> https://blog.rust-lang.org/2025/02/20/Rust-1.85.0.html
> 
> Some of the major updates:
> 
> - Update LIC_FILES_CHKSUM in libstd-rs and rust recipes.
> License-Update: Unicode license text is updated to Unicode-3.0
> License.
> https://github.com/rust-lang/rust/commit/6d2a3e9786ec43a0e0af20386e7046328296ac86

Thanks, this one step in the right direction but there is a
corresponding change missing. The recipe says:

LICENSE = "(MIT | Apache-2.0) & Unicode-TOU"

Does this not need to be updated to include Unicode-3.0?

That commit mentioned that the SPDX identifier exists:

https://spdx.org/licenses/Unicode-3.0.html

so I suspect it should at least be mentioned in LICENSE. I'm not if
other unicode licenses are present or not any more.

Cheers,

Richard



  reply	other threads:[~2025-03-31  6:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31  5:54 [PATCH v2 1/3] rust: Update "do_update_snapshot" task for rust-snapshot.inc Yash.Shinde
2025-03-31  5:54 ` [PATCH v2 2/3] rust: Upgrade 1.84.1->1.85.0 Yash.Shinde
2025-03-31  6:24   ` Richard Purdie [this message]
2025-03-31  7:16     ` [OE-core] " Yash Shinde
2025-03-31  8:17       ` Richard Purdie
2025-03-31 16:46   ` Khem Raj
2025-04-11  7:38     ` Martin Jansa
2025-04-15  9:04       ` Yash Shinde
2025-04-15 11:38         ` Martin Jansa
2025-04-15 15:45           ` Yash Shinde
2025-04-15 15:52             ` Martin Jansa
2025-04-15 15:58               ` Yash Shinde
2025-04-15 15:51           ` Yash Shinde
2025-04-15 15:53             ` Yash Shinde
2025-03-31  5:54 ` [PATCH v2 3/3] rust: Upgrade 1.85.0->1.85.1 Yash.Shinde

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=6a0be636d9c44b3166ac50e42c34aedf13a1be28.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=Yash.Shinde@windriver.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