Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] connman: fix nftables dependency
Date: Mon, 19 Jun 2017 13:06:41 +0100	[thread overview]
Message-ID: <1497874001.25895.5.camel@andred.net> (raw)
In-Reply-To: <20170619140225.5cfdc2a6@t460p>

On Mon, 2017-06-19 at 14:02 +0200, Andreas Oberritter wrote:
> Hi André,
> 
> On Mon, 19 Jun 2017 11:32:38 +0100
> André Draszik <git@andred.net> wrote:
> 
> > From: André Draszik <adraszik@tycoint.com>
> > 
> > When building with nftables support, connman doesn't ever
> > depend on the nftables command line tool.
> > 
> > connman will depend on libmnl and libnftnl at build and
> > run time. In addition, the nftables rules it creates
> > depend on various kernel modules being present.
> > 
> > Update the PACKAGECONFIG to reflect this.
> > 
> 
> packageconfig creates runtime dependencies for the modules you added. This
> will cause problems if the modules are built into the kernel binary. You
> should add runtime recommendations instead.

But they should all be fulfilled because of PACKAGES_DYNAMIC in
kernel.bbclass, no?

Cheers,
Andre'



  reply	other threads:[~2017-06-19 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 10:32 [PATCH] connman: fix nftables dependency André Draszik
2017-06-19 12:02 ` Andreas Oberritter
2017-06-19 12:06   ` André Draszik [this message]
2017-06-19 12:30     ` Andreas Oberritter
2017-06-19 12:40 ` Maxin B. John
2017-06-26 10:08 ` [PATCH v2 1/2] [RFC] base.bbclass: extend PACKAGECONFIG to also allow RRECOMMENDS André Draszik
2017-06-26 10:08   ` [PATCH v2 2/2] connman: fix nftables dependency André Draszik

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=1497874001.25895.5.camel@andred.net \
    --to=git@andred.net \
    --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