Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Nicolas Wirth" <nicolas.wirth@speedgoat.ch>
To: yocto@lists.yoctoproject.org
Subject: Re: How to switch between package version ?
Date: Wed, 16 Aug 2023 07:45:16 -0700	[thread overview]
Message-ID: <29355.1692197116432631142@lists.yoctoproject.org> (raw)
In-Reply-To: <ZNy7lBOvfDQheQ5j@nuoska>

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

I wasn't aware of BBMASK; that's useful, thank you.

I find it becoming clearer for me. However, I'm wondering how to address version conflicts in the following scenario:

* GCC 11.2 in the Honister branch
* Boost 1.74 in the Gatesgarth branch

I require the use of both these versions. Although they are both present in the meta layer, they exist on separate branches. What would be the solution in this case? Would it involve having two clones of the layer on my build host? Or perhaps writing my own Boost 1.74 recipe?

Neither option appears to be straightforward to me. Yet, this doesn't seem like an uncommon scenario. Others must have encountered the need for different recipes from the same layer but belonging to different branches. Is there a clear workflow for handling this?

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

  reply	other threads:[~2023-08-16 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 10:54 How to switch between package version ? Nicolas Wirth
2023-08-16 11:13 ` [yocto] " Mikko Rapeli
2023-08-16 11:55   ` Nicolas Wirth
2023-08-16 12:05     ` [yocto] " Mikko Rapeli
2023-08-16 14:45       ` Nicolas Wirth [this message]
2023-08-16 15:02         ` Alex Kiernan
2023-08-16 15:30           ` Alexander Kanavin
2023-08-16 15:32       ` Alexander Kanavin
2023-08-17  4:41         ` Mikko Rapeli
2023-08-17  7:37           ` Alexander Kanavin
     [not found]             ` <177BD8C48AE805D0.8497@lists.yoctoproject.org>
2023-08-17  7:47               ` Mikko Rapeli
2023-08-17 10:51                 ` Nicolas Wirth

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=29355.1692197116432631142@lists.yoctoproject.org \
    --to=nicolas.wirth@speedgoat.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox