All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yoann.congal@smile.fr, 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 16:55:01 +0000	[thread overview]
Message-ID: <d17f26cf2f1ee24072c836c84b6ab8cc4e7dd79d.camel@linuxfoundation.org> (raw)
In-Reply-To: <DH62AM0LD7ST.12CQ28MWFWBFR@smile.fr>

On Wed, 2026-03-18 at 17:51 +0100, Yoann Congal via lists.openembedded.org wrote:
> 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 :/

The other question that needs to be asked is why would you even need
tcp-wrappers-native? Why are you creating TCP services using the native
tools in a build? It doesn't make any sense.

We've had a flood of these "extend for native/nativesdk" patches and
I'm afraid I'm leaning toward saying no to all of them until we better
understand the actual use cases and make sure this isn't just a random
dependency explosion as people haven't actually thought about the
dependencies.

Cheers,

Richard


      reply	other threads:[~2026-03-18 16:55 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 ` [OE-core] " Yoann Congal
2026-03-18 16:55   ` Richard Purdie [this message]

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=d17f26cf2f1ee24072c836c84b6ab8cc4e7dd79d.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=deeratho@cisco.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    /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.