All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org>
To: Alex Kiernan <alex.kiernan@gmail.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
	 OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/2] rust: Enable building rust from stable, beta and nightly channels
Date: Thu, 15 Dec 2022 09:38:14 -0700	[thread overview]
Message-ID: <CAHMutrZnL2e4_7AuPkacEb-Rgyw0cb7eaErjWRuXZYXu_fUZgw@mail.gmail.com> (raw)
In-Reply-To: <CAO5Uq5S2reaaVJe7hZwL2okWjKBbVhU_=g6bMjguQ7T9UNC-Vw@mail.gmail.com>

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

On Thu, 15 Dec 2022 at 09:08, Alex Kiernan <alex.kiernan@gmail.com> wrote:

> On Thu, Dec 15, 2022 at 3:38 PM Alejandro Hernandez Samaniego
> <alejandro@enedino.org> wrote:
> >
> >
> >
> > On Thu, Dec 15, 2022, 3:05 AM Alexander Kanavin <alex.kanavin@gmail.com>
> wrote:
> >>
> >> On Thu, 15 Dec 2022 at 08:32, Alejandro Hernandez Samaniego
> >> <alejandro@enedino.org> wrote:
> >> > +RUST_VERSION = "1.65.0"
> >> > +SRC_URI += "
> https://static.rust-lang.org/dist/rustc-${RUST_VERSION}-src.tar.xz;name=rust
> "
> >>
> >> Adding a manually set variable adds friction to updates. Can
> >> RUST_VERSION be set instead with a helper @function from PV?
> >
> >
> > Hey Alex,
> >
> > I agree, and ideally yes, I tried to set it automatically to PV, but,
> sadly it conflicts if we try to include rust-source.inc from a non-rust
> recipe (This is necessary for some recipes that need to have rust source
> available to them) since it uses the PV set from that recipe instead.
> >
>
> Is this different cargo/rust versions, or something else you have?
>
> Basically I'm on the same page as Alex - updating this recipe is
> already quite painful, making it any worse doesn't seem like a great
> idea, but I guess you could argue that rust/cargo already conflate
> their versions in the current usage.
>

I'm referring to any recipe that could include rust-source.inc, if
RUST_VERSION ?= ${PV} for example,
 for rust recipes that works fine because RUST_VERSION would expand to
1.65.0 today, but lets say
recipe foo_1.0.1.bb needs rust-source.inc to recompile built-in crates, in
that case RUST_VERSION
would expand to 1.0.1 instead.

While I agree its not ideal, in my opinion this approach provides more
consistency with the drawback of
 modifying that variable on upgrades, however I also think that requiring
rust-source.inc is seldom the
case, hence the other option is to keep RUST_VERSION ?= ${PV} and hardcode
it on every recipe that
would require this flow.

Alejandro



>
> --
> Alex Kiernan
>

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

  reply	other threads:[~2022-12-15 16:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  7:32 [PATCH 1/2] rust: Enable building rust from stable, beta and nightly channels Alejandro Enedino Hernandez Samaniego
2022-12-15  7:32 ` [PATCH 2/2] rust: Enable baremetal targets Alejandro Enedino Hernandez Samaniego
2022-12-15  9:04 ` [OE-core] [PATCH 1/2] rust: Enable building rust from stable, beta and nightly channels Alexander Kanavin
2022-12-15 15:38   ` Alejandro Enedino Hernandez Samaniego
2022-12-15 16:08     ` Alex Kiernan
2022-12-15 16:38       ` Alejandro Enedino Hernandez Samaniego [this message]
2022-12-15 18:01         ` Alexander Kanavin
     [not found]         ` <1731096B411C6A99.9432@lists.openembedded.org>
2022-12-15 18:02           ` Alexander Kanavin
2022-12-15 18:11             ` Alejandro Enedino Hernandez Samaniego
2022-12-15 18:23               ` Alejandro Enedino Hernandez Samaniego
2022-12-15 18:31                 ` Alexander Kanavin
2022-12-15 21:36                 ` Alex Kiernan
2022-12-15 21:45                   ` Alejandro Enedino Hernandez Samaniego
2022-12-15 22:33                     ` Alex Kiernan
2022-12-17  1:20                       ` Alejandro Enedino Hernandez Samaniego
2022-12-17 17:11                         ` Alex Kiernan

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=CAHMutrZnL2e4_7AuPkacEb-Rgyw0cb7eaErjWRuXZYXu_fUZgw@mail.gmail.com \
    --to=alejandro@enedino.org \
    --cc=alex.kanavin@gmail.com \
    --cc=alex.kiernan@gmail.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 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.