[yocto] Remove nfs packages from image

[Marek Słomiany]

I have managed to track down what was including nfs-utils.
What I have done is, I think, worth to mention for future:
I have added BBMASK in my conf/local.conf to mask nfs-utils.bb recipe, than
tried to build my image.
As expected, build failed because nfs-utils recipe was required but not
found.
In the failure log the chain of includes/inherits was shown and the thing
that required nfs-utils was packagegroup-core-full-cmdline.
Thanks for your help.

Kind regards,
Marek

pt., 2 lut 2018 o 14:43 użytkownik Alexander Kanavin <
alexander.kanavin at linux.intel.com> napisał:

> On 02/02/2018 03:23 PM, Marek Słomiany wrote:
>
> > It's still on target:
> > root at target# opkg list |grep nfs
> > libnfsidmap0 - 0.25-r0
> > nfs-utils - 2.1.1-r0
> > nfs-utils-client - 2.1.1-r0
> > nfs-utils-mount - 2.1.1-r0
> >
> > While checking for any nfs-things using "bitbake <image> -e |grep -v ^#
> > |grep -i nfs" the only interesting thing I got is this:
> > EXCLUDE_FROM_WORLD_pn-unfs3_libc-musl="1"
> > FEATURE_PACKAGES_nfs-client="packagegroup-core-nfs-client"
> > FEATURE_PACKAGES_nfs-server="packagegroup-core-nfs-server"
> >
> > from which first one is not the thing, and two following are
> > from /meta/classes/core-image.bbclass and if I'm correct it's just
> > defining what will happen when I add nfs-client or nfs-server to
> > IMAGE_FEATURES.
> > Maybe I should delete manually some sstate or something?
>
> I'd say first inspect log.do_rootfs for your image, and maybe there are
> clues in it as to why these packages get pulled in. You might have a
> depdendency on them somewhere else.
>
> Alex
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180205/9b99e6cf/attachment.html>