08:53 <dvergatal> RP: around?

09:31 <rty> hi, people. I want to conditionally add bblayers based on the value of a variable, e.g. via python. is this approach possible/feasible? I have many different "projects" that use some combination of distros and machines and alter the packages in the final image in "project"-specific ways. I created a layer for each "project". now, I want to create some table/mapping that adds the correct layers at

09:31 <rty> runtime based on some "project" id, which is represented in a variable

09:32 <rty> s/alter the packages/alter the recipes/

11:46 <rty> regarding my question, I decided to try something similar to https://stackoverflow.com/questions/69676390/excluding-yocto-meta-layer-depending-on-a-variable-value . let's see how it goes...

14:25 <Xogium> is there a way to list the distro features one can enable ? I mean for example if I wanted to enable sysvinit support in systemd... I read the documentation about features in the manual, but I don't understand how one can figure out which features are present or not in a distro or how to enable them

14:26 <LetoThe2nd> Xogium: no, because distro features can essentially be defined on the fly. in the end its just a list of strings with arbitrary meaning.

14:27 <Xogium> so... How am I meant for example to list all the systemd things I could configure ?

14:27 <Xogium> that part is still very confusing to me

14:28 <Xogium> I have a hard time getting away from the menuconfig model, I think ^^

14:31 <Xogium> I'm also required to read the manuals one by one in individual pages format, because it turns out the all in one mega manual is SO large my screen reader chokes on it and crashes

14:37 <rty> I get a ParseError if I try sticking python () { ... } in bblayers.conf. can I not run anon python in bblayers, in .conf files, or am I making a silly mistake?

14:44 <LetoThe2nd> Xogium: the question is not "what can i configure", because the answer is "everything". it is more like "what are common options for a given recipe?", and in that case the answer is "look at the recipes PACKAGECONFIG items"

14:45 <LetoThe2nd> Xogium: a distro config entry is conceptually meant to affect multiple places across the whole resulting distribution.

14:46 <Xogium> so using distro_feature to add sysvinit isn't proper ?

14:46 <Xogium> unless you want the entire distro to be that way that is

14:48 <LetoThe2nd> Xogium: bingo.

14:48 <Xogium> I think I'm slowly getting the idea

14:49 <LetoThe2nd> Xogium: i mean... look at the word "distro feature". it *might* *remotely* *suggest* that it is about the distro, and not some random package.

14:49 <Xogium> I still think too simply, i.e: in term of firmware and not distribution

14:50 <LetoThe2nd> Xogium: i told you. Yocto always favors customizability and reproducibility.

14:52 <Xogium> yeah, I know :) it's just still difficult to wrap my head around it all

14:53 <Xogium> I think that list packageconfig in scripts/contrib might help figuring out things... I don't know yet though

15:02 <Guest93> Hi, I'm been faced with these two warning messages that I've been trying to resolve. The first warning message I appeared to of fix by adding `NO_GENERIC_LICENSE[BSD] = "LICENSE.txt"` to my bb recipe file. However, the second warning (the one for do_rootfs) is still there and can't quite shake it. Ideas?

15:02 <Guest93> > WARNING: python-pyserial-3.5-r0 do_populate_lic: QA Issue: python-pyserial: No generic license file exists for: BSD in any provider [license-exists]

15:02 <Guest93> > WARNING: rpi-test-image-1.0-r0 do_rootfs: QA Issue: The license listed BSD was not in the licenses collected for recipe python-pyserial [license-file-missing]

15:04 <Guest93> Maybe I have to create a patch for the `rpi-test-image` bb file that also adds the line `NO_GENERIC_LICENSE[BSD] = "LICENSE.txt"` to it? Maybe I'll give that a try real quick.

17:13 <dario> iirc poky uses more specific names like "BSD-2-clause", those should be properly known already, maybe you can use of of those in your recipe? maybe grep -r LICENSE in poky/meta dir

17:19 <rty> I am trying to use bitbake-diffsigs but the bitbake server has been starting for an eternity now. any ideas?

19:47 <Xogium> hmm meanwhile here trying to add something using packageconfig instead of distro_feature. I created my own layer as test and made something like recipes-core/systemd/systemd.bbappend. It's not willing to use it. If I add the version number of systemd, it tells me, no bb file in default match pattern

19:49 <rm5248> Hi, I'm trying to remove PAM from my yocto build as it is not needed for my purposes. I've added DISTRO_FEATURES:remove = "pam" to the image that I am building. It seems to remove it from DISTRO_FEATURES, but I still have the /etc/pam.d folder in the generated rootfs. Why might this be the case?

19:50 <rm5248> @Xogium did you try recipetool? e.g. recipetool newappend /path/to/layer systemd

19:51 <rm5248> if your append is working correctly it should show up with: bitbake-layers show-appends systemd

20:06 <Xogium> rm5248: I forgot about recipetool

20:09 <Xogium> hm I must have done something stupid manually ;) it works with the newappend