public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Isaac True <itrue@emlix.com>, isar-users@googlegroups.com
Subject: Re: [PATCH] linux-custom: Sync provides value with build profiles
Date: Mon, 10 Nov 2025 13:39:44 +0200	[thread overview]
Message-ID: <9ccf5d6d-2f67-4f03-ad30-3d94b8676c00@ilbers.de> (raw)
In-Reply-To: <48c754c9-6d5c-4612-b314-39cfc0cb0b75@emlix.com>

10/11/2025 13:20, Isaac True wrote:
> Hi,
>
> This could be simplified down to something like this which would avoid 
> creating new functions and be consistent with other places in 
> linux-custom.inc:
>
> RECIPE_PROVIDES:append = " ${@ bb.utils.contains('DEB_BUILD_PROFILES', 
> 'nolibcdev', '', 'linux-libc-dev linux-libc-dev-${DISTRO_ARCH}-cross', 
> d) }"
>
> What do you think?
>
> Cheers,
> Isaac
Hello Isaac,

The motivation was to keep the same format of deps declare as previously
(multi-line list), so it will be easier to maintain in the future.
So maybe something hybrid should be better, like:

RECIPE_PROVIDES:append = " ${@ bb.utils.contains('DEB_BUILD_PROFILES', 
'nolibcdev', '', d.getVar('RECIPE_PROVIDES_LIBC_DEV'), d) }"

I'm also not happy with RECIPE_PROVIDES_LIBC_DEV naming, but didn't came up
with better one.

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/9ccf5d6d-2f67-4f03-ad30-3d94b8676c00%40ilbers.de.

  reply	other threads:[~2025-11-10 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 11:06 Anton Mikanovich
2025-11-10 11:20 ` 'Isaac True' via isar-users
2025-11-10 11:39   ` Anton Mikanovich [this message]
2025-11-10 11:55     ` 'Jan Kiszka' via isar-users

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=9ccf5d6d-2f67-4f03-ad30-3d94b8676c00@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=itrue@emlix.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