public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <deeratho@cisco.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [openembedded-core][scarthgap][PATCH] tcp-wrappers: extend recipe for native/nativesdk builds
Date: Wed, 18 Mar 2026 17:51:16 +0100	[thread overview]
Message-ID: <DH62AM0LD7ST.12CQ28MWFWBFR@smile.fr> (raw)
In-Reply-To: <20260309145640.3432992-1-deeratho@cisco.com>

On Mon Mar 9, 2026 at 3:56 PM CET, Deepak Rathore via lists.openembedded.org wrote:
> From: Deepak Rathore <deeratho@cisco.com>
>
> Some SDK dependency chains require tcp-wrappers to be available
> as host/SDK artifacts. The current metadata only partially provides this,
> which can lead to dependency resolution failures when this recipe is pulled
> into SDK-oriented builds.
>
> This change does not alter target package behavior; it only enables required
> native/nativesdk variants for build and SDK integration paths.
>
> Signed-off-by: Deepak Rathore <deeratho@cisco.com>
>
> diff --git a/meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb b/meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb
> index bcd1d6f792..26eaeab1ac 100644
> --- a/meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb
> +++ b/meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb
> @@ -132,3 +132,4 @@ do_install () {
>  }
>  
>  FILES:${PN} += "${sysconfdir}/hosts.allow ${sysconfdir}/hosts.deny"
> +BBCLASSEXTEND = "native nativesdk"

That effectively create 2 new recipes tcp-wrappers-native and
nativesdk-tcp-wrappers. That is not a trivial change that I can take
without a clear and strong justification.

What "dependency resolution failures" did you see?

Also, can you check that tcp-wrapper-native builds on Fedora 41? This is
the scarthgap supported distro with the most recent GCC : gcc-14 (and it
usually trigger build failures on old/unmaintained packages)

Finally, OE-Core master did remove the recipe for it being really
unmaintained[0]. This is not a good sign :/

[0]: https://git.openembedded.org/openembedded-core/commit/?h=master-next&id=e556df28f47e754b53e1f46c97dde2b19fd8fad1

Regards,
-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-03-18 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 14:56 [openembedded-core][scarthgap][PATCH] tcp-wrappers: extend recipe for native/nativesdk builds Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-03-18 16:51 ` Yoann Congal [this message]
2026-03-18 16:55   ` [OE-core] " Richard Purdie

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=DH62AM0LD7ST.12CQ28MWFWBFR@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=deeratho@cisco.com \
    --cc=openembedded-core@lists.openembedded.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