On Thu, 15 Dec 2022 at 17:38, Alejandro Enedino Hernandez Samaniego
<[email protected]> wrote:
> 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.
Ok, I think what we should do first is to actually drop the version
from all of the .bb file names, and set it once, inside some .inc, and
probably next to SRC_URI and tarball checksum. Then this should allow
a convenient scheme for including and overriding things.
rust_1.65.0.bb - > rust.bb, and so on.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174587):
https://lists.openembedded.org/g/openembedded-core/message/174587
Mute This Topic: https://lists.openembedded.org/mt/95684480/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
