00:11 <Saur[m]> hushmoney: Run `bitbake -g <recipe>` to get the dependency graph for <recipe>. The search the produced `task-depends.dot` file for references to `libxcrypt`(which is what provides `virtual/crypt`).

04:12 <Yudjinn> Hello! I took some online courses a year ago going over the basics of yocto but I am starting up a job in 2 weeks that will be much more in depth and advanced yocto work. Can anyone recommend resources to brush up my skills again and best practices?

04:28 <yudjinn[m]> Swapped accounts, me still

14:32 <hushmoney> Saur[m]: thanks

15:21 <hushmoney> now i'm struggling with more of an organizational opinion question. i want to override the default PACKAGECONFIG for a recipe that's defined in a layer i don't own. where would you prefer to do this type of stuff from? i think my two options are to create a distro/include/mydistro-packageconfigs.inc similar (i already have mydistro-providers.inc, etc.), or would you rather see that in a .bbappend?

15:22 <hushmoney> having difficulty finding examples. what is conventional?

15:34 <hushmoney> now that i think of it, i think there are a lot of recipes that all inherit from the same bbclass and share the same PACKAGECONFIG set, so maybe i should think about how i can override them all with one distro setting. i think that makes the most sense

16:27 <RP> hushmoney: I'd probably do it as a distro config file

18:25 <vvn> hushmoney: either PACKAGECONFIG:append:pn-foo = " cfg1 cfg2" in your distro config file (or included fragment), or PACKAGECONFIG:append:mydistro = " cfg1 cfg2" in a foo_%.bbappend file in your distro layer.

21:07 <hushmoney> RP: vvn: thanks