10:24 <Entei[m]> I have played with default poky distribution for some days now, added packages to it, resized rootfs, enabled image features, even done some ISA tuning for the OS image. Now I wish to customize all aspects of the image, while inheriting most of poky's.

10:24 <Entei[m]> So far I mostly customized by directly editing the files in `meta/conf` , which would be deemed the wrong way to do it by Yocto's layer approach. Also I wish to customize things like the package naming scheme (right now there's r0 in it), the kernel name, gcc target name etc.

10:24 <Entei[m]> How do I go about this? Youtube videos only show building poky at best. I am reading the reference manual but the information feels too scattered. Also there's tons of variables.

10:24 <Entei[m]> How did you guys go about it?

10:45 <rpcme> I am looking at fixing YOCTO#14802 this weekend. I am aware of set_versions.py and such, but I am looking for the process on how docs are actually released so I know how the build gets triggered centrally and have awareness how the variables that affect versioning get set. I couldn't get that figured through

10:45 <rpcme> https://wiki.yoctoproject.org/wiki/Yocto_Release_Engineering so if someone could point me in the right direction that would be awesome.

10:49 <rpcme> I also looked at https://wiki.yoctoproject.org/wiki/Documentation_Review which is named in the bug but... it's still a bit challenging to decode.

11:27 <DvorkinDmitry> I ahve two kernel versions: _v0 and _v1. I need to install kernel-module-v0 or kernel-module-v1 into the image depending on kernel version I choosed with PREFFERED_...

11:27 <DvorkinDmitry> how to do this correctly?

11:36 <RP> rpcme: the docs are now basically entirely auto generated

11:36 <RP> rpcme: you can see the docs builds here: https://autobuilder.yoctoproject.org/typhoon/#/builders/114

11:37 <RP> rpcme: you can see it runs /home/pokybuild/yocto-worker/docs/yocto-autobuilder-helper/scripts/run-docs-build /home/pokybuild/yocto-worker/docs /home/pokybuild/yocto-worker/docs/yocto-docs /home/pokybuild/yocto-worker/docs/bitbake

11:38 <RP> rpcme: i.e. https://git.yoctoproject.org/yocto-autobuilder-helper/tree/scripts/run-docs-build

11:40 <rpcme> RP: this is very useful I will work backwards from this. In the defect there is some mention of the Poky versioning tie-in so it's helpful for me to get the whole landscape before I write what to change before actually patching anything. The whole .999 thing really bugs me (why I put in the bug in the first place) and I really don't know the

11:40 <rpcme> history behind adding .999 which is also what I mentioned in the defect

11:47 <RP> rpcme: The reason is you have the released versions but you also have the "latest build of the docs from the branch" which don't have a version yet

11:54 <rpcme> RP: Ok great - let me see if I can swimlane this or something to get it sorted in my head. I think I understand the timing issue (bleeding edge vs release tagged version). Maybe where I'm confused is 999 is being used instead of some kind of variable marker like X. But I need to understand deeper before trying to resolve my initial error which is

11:54 <rpcme> the docs autogenerate a broken link download so maybe nothing needs to be fixed in code, just say wherever there is a download link that the 999 marker is bleeding edge and won't have a download location

11:55 <RP> rpcme: or, we make those download links point to the last release instead of bleeding edge

11:56 <RP> rpcme: it just needs someone to think all the pieces through, I don't think anyone has found the time for that. I agree we shouldn't have broken links

12:17 <mischief> Entei[m]: make a layer

12:18 <rpcme> RP: yes let me do some writing to think through it. We've both been doing build systems long enough to know that changes like this have dark corners :)

12:19 <Entei[m]> mischief: Did that. But not sure how to inherit properties from other layers

12:19 <RP> rpcme: exactly!

12:20 <RP> rpcme: those scripts should be able to run locally btw, maybe with the final copy to location disabled

12:20 <mischief> Entei[m]: for us, we have poky/meta-oe and our own layer, with a custom site.conf/machines and image/packagegroup recipe, and recipes/bbappends on top of that

12:21 <mischief> pretty much everything can be overridden that way

12:22 <Entei[m]> mischief: Do you have a public repo or know of any where I could get inspiration from?

12:24 <mischief> i don't. our firmware is closed unfortunately.

12:25 <mischief> i can describe our basic layout but i'm not sure it really conforms to yocto ideals :-)

12:26 <mischief> we set TEMPLATECONF for meta-$company/conf, and in there just have a bblayers.conf.sample with our layer setup + poky/meta-oe

12:26 <mischief> from there you can write any recipes or bbappends for upstream in meta-$company/ along with machines in conf or whatever

12:31 <mischief> maybe https://github.com/Xilinx/meta-petalinux is a good example? but probably complex for a starting point

12:31 <mischief> for us, we just have poky/meta-oe as submodules but you could probably also use repo

13:31 <rpcme> RP: I updated the ticket to give the only three options I see without fundamentally changing the .999 scheme (which I think is an OK compromise but might want to get its use documented in WIki or something) - I think the first option is the least painful but would require an additional step in new release seeding. Maybe it should be discussed in

13:31 <rpcme> the list.

14:27 <Entei[m]> <mischief> "maybe https://github.com/Xilinx..."; <- yeah this looks too complicated, too many things in every file....

16:28 <DvorkinDmitry> I have two kernel versions: _v0 and _v1. I need to install kernel-module-x0 or kernel-module-x1 into the image depending on kernel version I choose. How to do that?