From: "Quentin Schulz" <quentin.schulz@streamunlimited.com>
To: Zoltan Kerenyi Nagy <kerenyi.nagy.zoltan@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: Private: Re: [yocto] network-manager #yocto #nmcli
Date: Tue, 20 Oct 2020 12:03:00 +0200 [thread overview]
Message-ID: <20201020100300.wazte5ty3trgigdp@qschulz> (raw)
In-Reply-To: <2995.1603187726816843811@lists.yoctoproject.org>
Please keep the mailing list in copy so everyone can benefit from your
progress/the solution, thanks!
On Tue, Oct 20, 2020 at 02:55:26AM -0700, Zoltan Kerenyi Nagy wrote:
> I'll do this, thanks.
>
> Interestingly there is a line in the recipe file, which suggests that nmtui will be included.
> -with-nmtui=yes \
This is an option at build time (i.e. for the **recipe**). It just
configures the piece of SW you're trying to build.
A bitbaked recipe's outcome is **packages**. In **most** cases, the main
package is named after the recipe (which is usually a source of
confusion for people). However, to slim down the main package, most
recipes split their output into multiple packages.
In your case, networkmanager is configured to be compiled with nmtui
support. However, the recipe is asked to put the resulting
binaries/conf files/libs into a separate package (called
networkmanager-nmtui).
When you're installing networmanager, you're not installing the whole
outcome of networkmanager recipe (nor the recipe itself) but the main
package that is the outcome of said recipe. It might not contain all you
want, hence the need for installing other packages for enabling all
features you want/need.
Hope this helps,
Quentin
next prev parent reply other threads:[~2020-10-20 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 8:48 network-manager #yocto #nmcli Zoltan Kerenyi Nagy
2020-10-20 8:57 ` [yocto] " Quentin Schulz
[not found] ` <2995.1603187726816843811@lists.yoctoproject.org>
2020-10-20 10:03 ` Quentin Schulz [this message]
2020-10-20 13:51 ` Zoltan Kerenyi Nagy
2020-10-20 13:58 ` [yocto] " Quentin Schulz
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=20201020100300.wazte5ty3trgigdp@qschulz \
--to=quentin.schulz@streamunlimited.com \
--cc=kerenyi.nagy.zoltan@gmail.com \
--cc=yocto@lists.yoctoproject.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