**** BEGIN LOGGING AT Thu Mar 04 10:48:20 2021 Mar 04 12:21:22 JaMa: thanks Mar 04 17:40:00 A couple of weeks ago submitted a patch for meta-python2 to support some legacy code and systems but it never got picked in master-next. Any chance to add it? Mar 04 17:40:01 https://lists.openembedded.org/g/openembedded-devel/message/89728?p=,,,20,0,0,0::Created,,meta-python2,20,2,0,80884272 Mar 04 17:48:14 leon-anavi: I think that's a JaMa question, last few commits since moto-timo stepped down as maintainer of it seem to be from him Mar 04 17:49:13 leon-anavi: adding a new module at this point might be less appealing. Plus Kodi 19 switched to python3, I thought... Mar 04 18:43:07 zeddii: hey, let me know if you feel like taking a poke at something other than infrastructure and perf ;-) Mar 04 19:11:28 tlwoerner, he should try poking a bear Mar 04 19:26:21 lol Mar 04 19:30:45 armpit: actually the questions i have for zeddii are a result of my trying to make my BSP layer as nice as yours (i.e. using kernel config fragments and scc files etc) Mar 04 19:57:58 tlwoerner: here Mar 04 19:59:08 currently my BSP layer is using the in-kernel multi-defconfig for configuration Mar 04 19:59:24 zeddii: this works just fine, the boards all boot, not a problem Mar 04 20:00:21 however… the resulting kernel is 11MB in size and including everything *and* the kitchen sink. every conceivable platform is enabled, and a vast number of drivers that could never be needed Mar 04 20:00:51 zeddii: i was thinking of using kernel fragments to trim down the config and, ideally, customize them for each board Mar 04 20:01:17 but creating the fragments to turn off vast swaths of kernel config is getting tedious Mar 04 20:01:53 * zeddii nods. tearing down is harder than building up. Mar 04 20:02:00 i was wondering if you had a recommendation for a way of starting with a very small, minimal, config (and then adding to it)? Mar 04 20:02:15 is there a "make smallconfig" or something? Mar 04 20:03:44 also, is the ordering of the fragments significant? i was thinking of spreading the fragments out between various config files in the BSP layer Mar 04 20:04:01 I have a script that has bit rotted a bit that can take a defconfig and yank out fragements from it. That in theory, can then be applied on top of a allnoconfig and you'll get a small, but booting config. Mar 04 20:04:12 let me go and find that script and see what it looks like. Mar 04 20:04:28 the ordering does matter, in the sense that the last fragment will set the value. Mar 04 20:21:18 zeddii: interesting. how does the script work? i'm guessing it's more than just grepping for a CONFIGF_ value? Mar 04 20:21:30 s/CONFIGF_/CONFIG_ Mar 04 20:26:11 leon-anavi: I've just overlooked it, but adding new module and in older version than what is already there (recipes-devtools/python/python-pygobject_3.34.0.bb) is indeed less appealing (if LibreELEC settings is the only user which needs that, then I would leave it in the layer with this add-on) Mar 04 20:31:17 JaMa, it is up to you. version 2.28.7 is without GI because of this in my opinion it makes sense to have it for backward compatibility. Anyway python2 is OEL and meta-python2 is kept for backward compatibility so I think another version of python-pygobject in there won't hurt anyone. I guess Kodi 18 plugins and older are not the only use cases. Mar 04 20:33:49 tlwoerner: yah. it runs some iterative configuration runs of the kernel and looks for what you do/don't need. I'm sure i can make it better now, so I'm trying to wrap my head around it at the moment. Mar 04 20:35:43 zeddii: or you could make it available to me and i'll take a look? i really appreciate the advise, but i don't want to keep you from other things. Mar 04 20:35:45 *sorry EOL (on OEL) :) Mar 04 20:35:50 not Mar 04 20:36:25 oh man, I am making a typo on every line :) Mar 04 20:36:36 my other thought is to do a menuconfig and disable all the drivers, platforms, and other non-core things manually, turn that into a defconfig, and build from there Mar 04 20:42:26 That can work as well. The problem is that my script is using my old audit output, I need to tweak it a bit at least. I'll try for a bit, and if not, I can explain/writeup what it is doing. Mar 04 20:56:19 leon-anavi: won't hurt except me to maintain it :) I have also volunteered to maintain only python-native and possibly move it to separate layer while letting the rest rot away (as python-native is still unfortunately used by many projects during build like chromium etc) Mar 04 21:05:59 leon-anavi: if it's needed by other projects, then where they were getting it since 2016 when this older version was removed from oe-core? https://git.openembedded.org/openembedded-core/commit/?id=12d61ac95b6bfae60dd4a7c7239bc8b8b0bcafbb **** ENDING LOGGING AT Fri Mar 05 02:59:57 2021