All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Murray <scott.murray@konsulko.com>
To: yocto@lists.yoctoproject.org
Subject: [meta-lts-mixins][kirkstone/rust-1.68 RFC v2 PATCH 0/2] Proposed Kirkstone Rust 1.68 mixin
Date: Sun,  7 May 2023 13:17:21 -0400	[thread overview]
Message-ID: <cover.1683479537.git.scott.murray@konsulko.com> (raw)

These patches comprise my proposed kirkstone/rust-1.68 branch for the
meta-lts-mixins repo.  The initial check-in backports the Rust 1.68.1
support from mickledore branch as it stands for 4.2.0, then I have
separately applied the Rust 1.68.2 upgrade from master that Steve has
queued up for Mickledore.

The README in the initial check-in provides some details on the
backporting of the librsvg recipe versus not doing so for
python3-cryptography.  I did double-check this again, and I do not see
a way to retrofit the librsvg recipe with a bbappend, as the bit to be
changed is in a do_compile:prepend.  The other recipe that I've
discovered with a similar issue is mozjs-91 in meta-openembedded; it
effectively needs a replacement do_compile to pick up the RUST_HOST_SYS
change.  That could possibly be handled with a bbappend in dynamic layer
in this mixin, but I have decided to consider it outside the scope for
now.

v2: Remove Rust-related patches from master that Steve does not have
    queued for Mickledore. If they do later get backported, they can
    be re-added as required.

Alex Kiernan (1):
  rust: Upgrade 1.68.1 -> 1.68.2

Scott Murray (1):
  Initial check-in

-- 
2.39.2



             reply	other threads:[~2023-05-07 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-07 17:17 Scott Murray [this message]
2023-05-07 17:17 ` [meta-lts-mixins][kirkstone/rust-1.68 RFC v2 PATCH 1/2] Initial check-in Scott Murray
2023-05-07 17:17 ` [meta-lts-mixins][kirkstone/rust-1.68 RFC v2 PATCH 2/2] rust: Upgrade 1.68.1 -> 1.68.2 Scott Murray

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=cover.1683479537.git.scott.murray@konsulko.com \
    --to=scott.murray@konsulko.com \
    --cc=yocto@lists.yoctoproject.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.