How to properly enable PAM integration - docs no longer valid?

How to properly enable PAM integration - docs no longer valid?

[Carlos Rafael Giani]

According to this document:

   https://wiki.yoctoproject.org/wiki/PAM_Integration

PAM can be enabled by adding this line to local.conf:

   DISTRO_FEATURES_append += " pam"

In newer Yocto versions, this would be:

   DISTRO_FEATURES:append += " pam"

and this works. I *had* to use "+=" instead of "=" here, otherwise pam 
would not be added correctly.

But, then I get this warning:

   WARNING: DISTRO_FEATURES:append += is not a recommended operator 
combination, please replace it

So, how am I supposed to enable PAM in local.conf if I need to enable it 
quickly for a test by using poky and can't set up my own distro right now?

RE: [OE-core] How to properly enable PAM integration - docs no longer valid?

[Peter Kjellerstedt]

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Carlos Rafael Giani via
> lists.openembedded.org
> Sent: den 29 januari 2022 05:19
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] How to properly enable PAM integration - docs no longer
> valid?
> 
> According to this document:
> 
>    https://wiki.yoctoproject.org/wiki/PAM_Integration
> 
> PAM can be enabled by adding this line to local.conf:
> 
>    DISTRO_FEATURES_append += " pam"
> 
> In newer Yocto versions, this would be:
> 
>    DISTRO_FEATURES:append += " pam"
> 
> and this works. I *had* to use "+=" instead of "=" here, otherwise pam
> would not be added correctly.
> 
> But, then I get this warning:
> 
>    WARNING: DISTRO_FEATURES:append += is not a recommended operator
> combination, please replace it
> 
> So, how am I supposed to enable PAM in local.conf if I need to enable it
> quickly for a test by using poky and can't set up my own distro right now?

The correct form is:

DISTRO_FEATURES:append = " pam"

There should be no reason to use += above (which is also why it now 
generates a warning if you do).

You can always check the value of a variable and how it got defined by 
using `bitbake -e`, or the new bitbake-getvar, e.g., `bitbake-getvar 
DISTRO_FEATURES`.

//Peter