public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [RFC 0/4] Warn on PN usage for virtual packages
Date: Fri, 16 Feb 2024 16:34:22 +0200	[thread overview]
Message-ID: <20240216143426.3490967-1-amikan@ilbers.de> (raw)

Compat and native packages can fail in case variables will have PN in
their content. For correct behaviour BPN (which is PN without suffix)
should be used instead.
We are hiding PN->BPN fallback fix from recipe authors but should warn
them to force moving to BPN usage.
There are also some PN usages in Isar need to be fixed.

This patchset should be placed on top of:
[PATCH v2 0/4] Fix SRC_URI:remove ignoring

Sending it as RFC because of high influence on downstreams by flooding
build log with new warnings.

Anton Mikanovich (4):
  multiarch: Add warning on PN usage fallback
  meta/conf/bitbake.conf: Set global BPN
  base: Fix FILESPATH value for -native and -compat
  hello: Use BPN instead of PN

 meta-isar/recipes-app/hello/hello.bb | 2 +-
 meta/classes/base.bbclass            | 2 +-
 meta/classes/multiarch.bbclass       | 4 ++--
 meta/classes/sdk.bbclass             | 1 -
 meta/conf/bitbake.conf               | 1 +
 5 files changed, 5 insertions(+), 5 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-02-16 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 14:34 Anton Mikanovich [this message]
2024-02-16 14:34 ` [RFC 1/4] multiarch: Add warning on PN usage fallback Anton Mikanovich
2024-02-16 14:34 ` [RFC 2/4] meta/conf/bitbake.conf: Set global BPN Anton Mikanovich
2024-02-16 14:34 ` [RFC 3/4] base: Fix FILESPATH value for -native and -compat Anton Mikanovich
2024-02-16 14:34 ` [RFC 4/4] hello: Use BPN instead of PN Anton Mikanovich

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=20240216143426.3490967-1-amikan@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /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