00:29 <vvn> Is it better to assign the CI/CD build number to BUILDNAME or IMAGE_VERSION_SUFFIX?

18:02 <khem> RP: I sent RFT patches for glibc 2.40

18:08 <temp64> Hi, I've been reading about Yocto all day but I'm not quite sure if it's the proper tool for my use case. I need to find an automated way to create a very minimal Linux image for a bunch of (slightly different) ASRock DeskMini PCs where I get to control the kernel configuration, what init it runs, compile-time configuration of packages, etc. Is it

18:08 <temp64> possible to accomplish with Yocto without too much friction?

18:08 <temp64> Asking because the learning curve seems to be steep and I'm not sure if there's an equivalent of Docker's "FROM scratch", so to say.

18:11 <khem> temp64:welcome to the community ! I must say yocto is very much a fit for what you want to achieve

18:12 <khem> for learning curve, I would suggest to go through quick guide https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html

18:13 <khem> and then try to build a core-image-minimal for say qemux86-64

18:13 <khem> https://docs.yoctoproject.org/what-i-wish-id-known.html is also good

18:14 <khem> then the mega-manual is something you want to keep handy for reference and ask questions here

18:15 <khem> there is also yocto@yoctoproject.org mailing list where you can find discussions in past which may solve some issues you might be seeing or you can ask quesitons there too

18:32 <temp64> Thanks, I'll check those out. I actually already built core-image-minimal and ran it in QEMU, worked perfectly fine. I then started going through the files and it seemed like all of those reference images inherit from core-image, which made me wonder if there's a minimal set of "untouchable" packages all images have to contain.

18:37 <temp64> Hence my "FROM scratch" concern above, on the surface (and looking at some random blogs), it seems like the go-to way of creating a custom image is to start from core-image and add recipes on top of it.

18:45 <marex> temp64: you can bend the result whichever way you see fit, the flexibility is usually overwhelming to newcomers

18:45 <marex> temp64: minimal is empty image

18:45 <marex> quite literally

18:47 <temp64> How does it boot if it's empty :D

18:48 <marex> temp64: you can build kernel and write it into some flash memory for example

18:51 <temp64> If I can do that and then just add packages on top one by one as if it was LFS then that's good enough for me.