All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nisha.M.Parrakat@bmw.de
To: openembedded-core@lists.openembedded.org
Subject: Re: [master][PATCH v2] librsvg: Fix do_package_qa error for librsvg
Date: Mon, 11 Mar 2024 05:15:02 -0700	[thread overview]
Message-ID: <27822.1710159302267588894@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj9v5FE6z552opyk_LsZpUx0nGpvGBiJ-wfUfA_YYGRhhQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

Thanks Alex for the reply.
So till now we are using meta-rust master along with the kirkstone yocto layers and are trying to understand if it makes sense to use it further.
We had a few questions for the maintainence of Rust.

1. Can we say, that oe-core will support Rust in future after Kirkstone  as a standalone (without any external dependency )?
2. We assume that kirkstone will stay with 1.59 and those who want later versions (1.68+)can use meta-lts-mixins
3. We have the following assumptions for meta-lts-mixins

a) We see kirkstone/rust-1.68, kirkstone/rust-1.70 branches.
A new branch will be created for a newer and stable rust version for example kirkstone/rust-1.75 .
b)  If *1* is not correct then we assume meta-lts-mixins will cater to all the LTS layers in future. That means we may see branches like scarthgap/rust-***

Thanks in advance for your reply !

regards,
Nisha Parrakat

[-- Attachment #2: Type: text/html, Size: 1599 bytes --]

  reply	other threads:[~2024-03-11 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  5:03 [OE-core][master][PATCH v2] librsvg: Fix do_package_qa error for librsvg Nikhil R
2024-03-08  7:01 ` Alexander Kanavin
2024-03-11 12:15   ` Nisha.M.Parrakat [this message]
2024-03-11 13:00     ` [OE-core] [master][PATCH " Alexander Kanavin

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=27822.1710159302267588894@lists.openembedded.org \
    --to=nisha.m.parrakat@bmw.de \
    --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 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.