Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mike Crowe" <mac@mcrowe.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Andre McCurdy <armccurdy@gmail.com>,
	Khem Raj <raj.khem@gmail.com>,
	Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	OE Core mailing list <openembedded-core@lists.openembedded.org>,
	chris_larson <chris_larson@mentor.com>
Subject: Re: [OE-core] [PATCH] sanity: skip make 4.2.1 warning for debian
Date: Wed, 27 Apr 2022 14:22:55 +0100	[thread overview]
Message-ID: <YmlDr4HMSXRpnAx4@mcrowe.com> (raw)
In-Reply-To: <c57ed8a714da34b9649a49e823a304e99dc6b7a8.camel@linuxfoundation.org>

On Wednesday 27 April 2022 at 11:40:49 +0100, Richard Purdie wrote:
> As far as I know, we don't use LSB_DISTRO_ADJUST in core at all. I suspect it
> should really probably be added to the lsb.py function in most cases. Is there
> any documentation or other info about when it should be applied and when it
> should not?

We used to use LSB_DISTRO_ADJUST to stop Debian minor release upgrades
causing sstate paths to change up until about five years ago when we
upgraded to an oe-core version that only considered the major version to be
important.

> I did have a look at
> https://git.yoctoproject.org/poky/commit/meta/classes/base.bbclass?id=096306ecd1bb80fe5e732584caca0172305628a2
> where it was introduced 10 years ago but there isn't much more info. 

I believe that we use the mapping in SSTATE_MIRRORS to do the equivalent of
what is described in that commit message:

  SSTATE_MIRRORS ?= "\
  file://debian ${OUR_SSTATE_DIR}/debian-10 \n \
  file://debian-11 ${OUR_SSTATE_DIR}/debian-10 \n \
  file://debian-10 ${OUR_SSTATE_DIR}/debian-10 \n \
  \
  file://debian-9 ${OUR_SSTATE_DIR}/debian-9 \n \
  file://.* ${OUR_SSTATE_DIR}/PATH \n \
  "

(Our autobuilders are running Debian 10 at the moment, so anyone running
Debian 11 can make use of sstate files they wrote to debian-10, but anyone
running Debian 9 cannot.)

I have no idea whether this works for the Red Hat world though.

HTH.

Mike.

  reply	other threads:[~2022-04-27 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 19:46 [PATCH] sanity: skip make 4.2.1 warning for debian Nicolas Dechesne
2022-04-26 20:50 ` [OE-core] " Andre McCurdy
2022-04-26 20:56   ` Khem Raj
2022-04-26 21:39     ` Andre McCurdy
2022-04-27 10:40       ` Richard Purdie
2022-04-27 13:22         ` Mike Crowe [this message]
2022-04-27 16:54         ` Andre McCurdy

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=YmlDr4HMSXRpnAx4@mcrowe.com \
    --to=mac@mcrowe.com \
    --cc=armccurdy@gmail.com \
    --cc=chris_larson@mentor.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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