Conditional inherit with PACKAGECONFIG

Conditional inherit with PACKAGECONFIG

[Robert Joslyn]

I'm trying to remove unnecessary packages from one of my images, and I
noticed that some conditional inherit lines don't work as I'd expect. In
my case, I'm trying to remove python, and the only recipe pulling in
python is btrfs-tools. The relevant parts of the btrfs-tools recipe (I'm
building on master):

PACKAGECONFIG ??= "python"

PACKAGECONFIG[python] = "--enable-python,--disable-python,python3-
setuptools-native"

inherit ${@bb.utils.contains('PACKAGECONFIG', 'python', 'distutils3-base', 
'', d)}

I have a bbappend removing the default PACKAGECONFIG containing "python",
but I still get a btrfs-tools package that RDEPENDS on python because the
distutils3-base class is still inherited. If I modify the btrfs-tools
recipe directly to be:

PACKAGECONFIG ??= ""

then I don't get python as an RDEPENDS. If I have the recipe modified like
this and then try to add python to PACKAGECONFIG from my bbappend, the
recipe fails to build because distutils3-base isn't inherited.

My guess is that the inherit lines are parsed and expanded before the
bbappend modification to PACKAGECONFIG are applied. The bitbake
documentation says you can have conditional inherits similar to this, but
it seems there is more nuance with how the parsing is done. How should
this be done if I want to be able to remove python from this recipe using
a bbappend? I'd prefer to avoid copying the recipe into my layer to make
the changes.

Thanks,
Robert

Re: [OE-core] Conditional inherit with PACKAGECONFIG

[Konrad Weihmann]

PACKAGECONFIG_pn-btrfs-utils = "foo bar" in local.conf or distro.conf 
should do what you had in mind.
But yes your observations are correct bbappends are applied *after* the 
initial recipe was parsed

On 04.12.20 05:34, Robert Joslyn wrote:
> I'm trying to remove unnecessary packages from one of my images, and I
> noticed that some conditional inherit lines don't work as I'd expect. In
> my case, I'm trying to remove python, and the only recipe pulling in
> python is btrfs-tools. The relevant parts of the btrfs-tools recipe (I'm
> building on master):
> 
> PACKAGECONFIG ??= "python"
> 
> PACKAGECONFIG[python] = "--enable-python,--disable-python,python3-
> setuptools-native"
> 
> inherit ${@bb.utils.contains('PACKAGECONFIG', 'python', 'distutils3-base',
> '', d)}
> 
> I have a bbappend removing the default PACKAGECONFIG containing "python",
> but I still get a btrfs-tools package that RDEPENDS on python because the
> distutils3-base class is still inherited. If I modify the btrfs-tools
> recipe directly to be:
> 
> PACKAGECONFIG ??= ""
> 
> then I don't get python as an RDEPENDS. If I have the recipe modified like
> this and then try to add python to PACKAGECONFIG from my bbappend, the
> recipe fails to build because distutils3-base isn't inherited.
> 
> My guess is that the inherit lines are parsed and expanded before the
> bbappend modification to PACKAGECONFIG are applied. The bitbake
> documentation says you can have conditional inherits similar to this, but
> it seems there is more nuance with how the parsing is done. How should
> this be done if I want to be able to remove python from this recipe using
> a bbappend? I'd prefer to avoid copying the recipe into my layer to make
> the changes.
> 
> Thanks,
> Robert
> 
> 
> 
> 
> 

Re: [OE-core] Conditional inherit with PACKAGECONFIG

[Robert Joslyn]

On 2020-12-04 03:40, Konrad Weihmann wrote:
> PACKAGECONFIG_pn-btrfs-utils = "foo bar" in local.conf or distro.conf
> should do what you had in mind.
> But yes your observations are correct bbappends are applied *after*
> the initial recipe was parsed

Thanks, I was able to get it working with this in my distro.conf:

PACKAGECONFIG_pn-btrfs-tools = ""
PACKAGECONFIG_pn-btrfs-tools-native = ""

It'd be nice if I could keep it contained within the bbappend, but this 
is better than copying the recipe to my layer.

Thanks,
Robert