**** BEGIN LOGGING AT Fri Feb 28 02:59:57 2020 Feb 28 07:30:06 armpit: shall i certify you? Feb 28 16:34:37 weird question. I'm getting multiple requests for what will essentially be distros. Does it make sense for me to create a meta-arm-distro layer to contain them all? Feb 28 16:42:19 yes Feb 28 16:42:25 plural? :O Feb 28 16:42:59 jonmason I've done the same in the past, but slightly differently. Everything in a single repository, related distros in the same layer.. Feb 28 16:43:33 i.e. meta-arm-distro (is a repository), and meta-arm-foobar/conf/distro/foobar.conf, foobar-tiny.conf, etc.. Feb 28 16:43:53 then new unrelated meta-arm-barfoo/conf/distro/barfoo.conf can come in, as long as it doesn't share any code with foobar Feb 28 16:44:11 (being a distro layer, I assume each may have a few bbappends as well) Feb 28 16:44:17 jonmason: heh ARM Linux sounds like a slippery slope ;) Feb 28 16:44:49 at WR we also had a 'core' distro that was depended on by other distro layers.. a wrlinux.inc, included by wrlinux.conf (distro).. then other wrlinux-variant could require the wrlinux.inc Feb 28 16:45:00 fray: do you have a reference I can look at? Feb 28 16:45:05 sec Feb 28 16:45:20 essentially, someone wants to upstream debug distro they are doing for openbmc Feb 28 16:45:30 https://github.com/WindRiver-Labs/wrlinux/tree/WRLINUX_10_19_BASE Feb 28 16:45:31 and we have this arm IOTA distro Feb 28 16:45:33 zeus based BTW Feb 28 16:45:48 you'll see the main directory is the core Wind River distribution layer.. Feb 28 16:45:51 and who knows what mbed Linux is going to end up as Feb 28 16:46:03 let me back up.. Feb 28 16:46:24 the main directory is the core Wind River 'generic work', not distro specific.. Feb 28 16:46:40 then there is a wrlinux-distro, wrlinux-cgl, wrlinux-overc and wrlinux-ovp for variant specific items.. Feb 28 16:46:58 each of those includes a file from the base that specifies the base system parameters common to all WR distros.. Feb 28 16:47:06 then the individual variants handle specifics Feb 28 16:47:16 https://github.com/WindRiver-Labs/wrlinux/tree/WRLINUX_10_19_BASE/wrlinux-distro/conf/distro Feb 28 16:47:31 this is a set of related 'general' distros.. graphics, installer, std-sato, tiny and 'base' Feb 28 16:48:02 I beleive CGL may inherit from here to start with, but something like overc likely doesn't .. only inheriting from the non-distro specific one Feb 28 16:48:27 (I'm not saying BTW this is the perfect way to do it, but it is one way to configure a broad number of distros and try to capture the common points) Feb 28 16:49:11 I'm not sure the overlap, if any, between these distros Feb 28 16:49:12 (and it passes the Yocto project compat testing) Feb 28 16:49:33 if there is no designed in overlap, then no reason to inherit each other... Feb 28 16:49:33 hahaha, layer compatability is a must Feb 28 16:50:28 fray: so, you think it is acceptable to put all the distro stuff simply in meta-arm and make my life easier? Feb 28 16:51:14 smurray: oh, everyone wants an Arm distro internally, but no one actually wants to do QA or anything that would actually make a distro usable... Feb 28 16:53:34 ya, I get that Feb 28 16:53:56 You want it in something clearly labeled as a distribution layer.. that way we all can ignore it when we have our own distros Feb 28 16:54:13 and if possible, limiting it to just configuration would be best Feb 28 16:55:19 jonmason: a clearly commented .inc file that can be pulled into a distro .conf to turn on stuff seems reasonable Feb 28 16:58:06 Let me herd the cats and we'll see what crap they put in the litterbox of meta-arm-distros ;-) Feb 28 17:11:54 I got a request from someone to include the wic-tools in the SDK. Does anyone know of a reason why I can't just add a nativesdk BBCLASSEXTEND to wic-tools? **** ENDING LOGGING AT Sat Feb 29 02:59:59 2020