All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 02/21] tcmode-default.inc: do not set PREFERRED_VERSION for toolchain items
Date: Wed, 14 Jul 2021 15:40:03 +0200	[thread overview]
Message-ID: <CANNYZj8hsgF9fkYinpzPdn6gsjhDXWB1YqTFEANGLNhg1vmn7w@mail.gmail.com> (raw)
In-Reply-To: <7304a1fd6d1ccfb9da17ec47125de68035094256.camel@linuxfoundation.org>

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

On Wed, 14 Jul 2021 at 14:55, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> At the very least the GCC variable is well used in other layers as it is
> hard to
> remember all the different bits of gcc that are listed here so I think
> that
> should stay. Some of these can probably be removed but I'm not sure how far
> we could/should go. glibc's list of recipes isn't trivial either...
>

I used layerindex to check. Alternative gcc versions are provided by
multiple layers (mostly arm-related), but an alternative older glibc is
only in meta-debian and that is using neither PREFERRED_VERSION directly
nor the *LIBCVERSION convenience (so not sure how it's meant to be used). I
will send a v2 with gcc added back.

Anyone else should probably just copy the PREFERRED_VERSION lines for what
they want to adjust into the layers directly. But let's see what Khem says
- I do think getting help from AUH/devtool in doing the updates fully, or
at least using 'devtool upgrade' locally to prepare the git trees for
manual patch rebasing is valuable.

Alex

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

  reply	other threads:[~2021-07-14 13:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 12:25 [PATCH 01/21] devtool: correctly handle non-standard source tree locations in upgrades Alexander Kanavin
2021-07-14 12:25 ` [PATCH 02/21] tcmode-default.inc: do not set PREFERRED_VERSION for toolchain items Alexander Kanavin
2021-07-14 12:55   ` [OE-core] " Richard Purdie
2021-07-14 13:40     ` Alexander Kanavin [this message]
2021-07-20 17:11       ` Denys Dmytriyenko
2021-07-14 14:01   ` Bruce Ashfield
2021-07-14 14:04     ` Alexander Kanavin
2021-07-14 17:07       ` Khem Raj
2021-07-14 12:25 ` [PATCH 03/21] llvm: make upgradable via devtool Alexander Kanavin
2021-07-14 17:18   ` [OE-core] " Khem Raj
2021-07-14 12:25 ` [PATCH 04/21] llvm: update 12.0.0 -> 12.0.1 Alexander Kanavin
2021-07-14 12:25 ` [PATCH 05/21] systemd: update 248.3 -> 249 Alexander Kanavin
2021-07-17 22:58   ` [OE-core] " Alexandre Belloni
2021-07-18  0:44     ` Khem Raj
2021-07-22 19:32       ` Alexander Kanavin
2021-07-14 12:25 ` [PATCH 06/21] xserver-xorg: update 1.20.11 -> 1.20.12 Alexander Kanavin
2021-07-14 12:25 ` [PATCH 07/21] libmodulemd: update 2.12.1 -> 2.13.0 Alexander Kanavin
2021-07-14 12:25 ` [PATCH 08/21] bluez5: upgrade 5.59 -> 5.60 Alexander Kanavin
2021-07-14 12:25 ` [PATCH 09/21] createrepo-c: upgrade 0.17.3 -> 0.17.4 Alexander Kanavin
2021-07-14 12:25 ` [PATCH 10/21] ethtool: upgrade 5.12 -> 5.13 Alexander Kanavin
2021-07-14 12:25 ` [PATCH 11/21] gtk+3: upgrade 3.24.29 -> 3.24.30 Alexander Kanavin
2021-07-14 12:25 ` [PATCH 12/21] harfbuzz: upgrade 2.8.1 -> 2.8.2 Alexander Kanavin
2021-07-14 12:25 ` [PATCH 13/21] iproute2: upgrade 5.12.0 -> 5.13.0 Alexander Kanavin
2021-07-14 12:25 ` [PATCH 14/21] libgit2: upgrade 1.1.0 -> 1.1.1 Alexander Kanavin
2021-07-14 12:26 ` [PATCH 15/21] mpg123: upgrade 1.28.0 -> 1.28.2 Alexander Kanavin
2021-07-14 12:26 ` [PATCH 16/21] mtools: upgrade 4.0.31 -> 4.0.32 Alexander Kanavin
2021-07-14 12:26 ` [PATCH 17/21] ruby: upgrade 3.0.1 -> 3.0.2 Alexander Kanavin
2021-07-14 12:26 ` [PATCH 18/21] stress-ng: upgrade 0.12.11 -> 0.12.12 Alexander Kanavin
2021-07-14 12:26 ` [PATCH 19/21] webkitgtk: upgrade 2.32.1 -> 2.32.2 Alexander Kanavin
2021-07-14 12:26 ` [PATCH 20/21] xwayland: upgrade 21.1.1 -> 21.1.2 Alexander Kanavin
2021-07-14 12:26 ` [PATCH 21/21] tcl: fix upstream version check Alexander Kanavin

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=CANNYZj8hsgF9fkYinpzPdn6gsjhDXWB1YqTFEANGLNhg1vmn7w@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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 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.