**** BEGIN LOGGING AT Wed Feb 09 02:59:56 2022
Feb 09 16:48:47 <fray> I thought you used to be able to use the override ":arm" for anything necessary for 32-bit arm systems, and aarch64 for 64-bit arm.  However, in honister I'm not seeing 'arm', but 'arm7a' as the override.  Did this change and I didn't notice?
Feb 09 16:51:41 <Crofton> I'm going to ask a stupid question
Feb 09 16:52:09 <Crofton> can I directly replace distutils-common-base.bbclass with setuptools3-base.bbclass
Feb 09 16:56:58 <JaMa> fray: both still exist (e.g. rpi4 still has arm and armv7ve)
Feb 09 16:59:00 <fray> Hmm.. I'm setting a distro feature based on the arch, and the feature isn't present when I do  :arm .. I'll need to investigate further.. maybe it's an all package and it's being sanitized or something
Feb 09 17:10:00 <smurray> Crofton: I see instances of that in the oe-core changes on master, perhaps try it
Feb 09 17:10:14 <smurray> Crofton: if not, you'll need to check with moto-timo
Feb 09 17:10:44 <Crofton> Yeah, something is building atm and that was going to be my first stab t making the message go away
Feb 09 17:39:41 <Ch^W_> The docs (and various other searching) are not 100% clear on variable semantics in (bbclass) shell functions. Is it safe to say that you can read exported variables, but not change them?
Feb 09 17:40:09 <Ch^W_> Whereas python functions have access to the full suite of functionality (e.g. setVar, apendVar, delVar, etc...)
Feb 09 18:27:11 <mru> Ch^W_: I don't see any mechanism for a shell function to change a variable
Feb 09 18:27:59 <mru> the script that is actually run is generated with the variables already expanded
Feb 09 19:30:55 <Ch^W_> mru: The useradd classes confused me a bit because it _seems_ like there is evidence for setting variables, but I agree with your statement - I could only ever do it with python functions.
**** ENDING LOGGING AT Thu Feb 10 02:59:56 2022