Thanks Alex for the reply.<br />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.<br />We had a few questions for the maintainence of Rust.<br /><br />
<div style="box-sizing: border-box; font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', system-ui, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Web', sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;">
<div>1. Can we say, that oe-core will support Rust in future after Kirkstone&nbsp; as a standalone (without any external dependency )? <br />2. We assume that kirkstone will stay with 1.59 and those who want later versions (1.68+)can use meta-lts-mixins<br />3. We have the following assumptions for meta-lts-mixins</div>
<div>
<div>&nbsp;</div>
<div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; a) We see kirkstone/rust-1.68, kirkstone/rust-1.70 branches. <br />&nbsp;&nbsp;&nbsp;&nbsp; A new branch will be created for a newer and stable rust version for example kirkstone/rust-1.75 .<br />&nbsp;&nbsp;&nbsp;&nbsp; b)&nbsp; If <strong>1</strong> 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-*** <br /><br />Thanks in advance for your reply !<br /><br />regards,<br />Nisha Parrakat<br /><br /></div>
</div>
</div>
</div>