Re: How to remove packages from Image coming because of RDEPENDS

Re: How to remove packages from Image coming because of RDEPENDS

[Lukasz Zemla]

On Tuesday, April 23, 2019 12:08 PM, Priyanshu Sharma wrote:
> How can we remove inclusion of any package which comes because some other package RDPENDS on it?
> For example, rpcbind recipe RDEPENDS on shadow and libpam packages, 
> because of which if IMAGE_INSTALL+="rpcbind" is mentioned in recipe ( 
> even though shadow and libpam are not added like this explicilty) , shadow and libpam packages get packaged in Image rootfs.
> This even includes any bin/sbin provided by shadow/libpam, even when they are not needed in rootfs.

> Is there an optimum way to control inclusion of RDEPENDS packages? One 
> way is to use ROOTFS_POST_PROCESS and remove specific files after do_rootfs task is done.
> But is there a way to remove entire package, instead of removing each file ?

Typically I create .bbappend with following:
RDEPENDS_${PN}_remove = "libpam"

But be careful what dependencies you remove. Sometimes Yocto sets too wide list of dependencies and in some configurations it is possible to remove them, but sometimes you may break some things. 

Best regards,
Lukasz Zemla

Re: How to remove packages from Image coming because of RDEPENDS

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]

On Tue, Apr 23, 2019 at 6:09 AM Priyanshu Sharma <
ms.priyanshu.sharma@gmail.com> wrote:

> Hi,
>
> How can we remove inclusion of any package which comes because some other
> package RDPENDS on it?
>
> For example, rpcbind recipe RDEPENDS on shadow and libpam packages,
> because of which if IMAGE_INSTALL+="rpcbind" is mentioned in recipe ( even
> though shadow and libpam are not added like this explicilty) , shadow and
> libpam packages get packaged in Image rootfs.
> This even includes any bin/sbin provided by shadow/libpam, even when they
> are not needed in rootfs.
>
> Is there an optimum way to control inclusion of RDEPENDS packages?
>

You need to somehow change the RDEPENDS via one of the mechanisms like
PACKAGECONFIG, or
by splitting the packaging into smaller, more specific sub-packages, etc.

If a package has a RDEPENDS on something else, you can't simply ignore it
or filter it out .. whoever
wrote the recipe is indicating that it is required at runtime. So if you
are saying that it isn't required at
runtime, you should be sending patches to the recipes (and using the
mechanisms like I mention
above) to explain why it really isn't a runtime dependency.

Bruce



> One way is to use ROOTFS_POST_PROCESS and remove specific files after
> do_rootfs task is done.
> But is there a way to remove entire package, instead of removing each file
> ?
>
> Warm Regards,
> Priyanshu Sharma
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

[-- Attachment #2: Type: text/html, Size: 3201 bytes --]

How to remove packages from Image coming because of RDEPENDS

[Priyanshu Sharma]

[-- Attachment #1: Type: text/plain, Size: 756 bytes --]

Hi,

How can we remove inclusion of any package which comes because some other
package RDPENDS on it?

For example, rpcbind recipe RDEPENDS on shadow and libpam packages, because
of which if IMAGE_INSTALL+="rpcbind" is mentioned in recipe ( even though
shadow and libpam are not added like this explicilty) , shadow and libpam
packages get packaged in Image rootfs.
This even includes any bin/sbin provided by shadow/libpam, even when they
are not needed in rootfs.

Is there an optimum way to control inclusion of RDEPENDS packages?
One way is to use ROOTFS_POST_PROCESS and remove specific files after
do_rootfs task is done.
But is there a way to remove entire package, instead of removing each file ?

Warm Regards,
Priyanshu Sharma

[-- Attachment #2: Type: text/html, Size: 924 bytes --]