geoff__ has quit [Remote host closed the connection]
Frank79 has joined #yocto
Frank79 has quit [Client Quit]
jmd has joined #yocto
amitk_ has joined #yocto
amitk has quit [Ping timeout: 265 seconds]
dmoseley_ has quit [Ping timeout: 265 seconds]
dmoseley has joined #yocto
druppy has joined #yocto
ablu has quit [Ping timeout: 265 seconds]
ablu has joined #yocto
Articulus has quit [Quit: Leaving]
Guest45 has joined #yocto
druppy has quit [Ping timeout: 244 seconds]
<Guest45>
Hi, i have yet two more general questions, when one wants to define their own distro.
<Guest45>
1. let's say you add a layer with your own recipes. Should it rather modify image, sth like `CORE_IMAGE:append = " my_additional_recipe my_other_recipe"` or perhaps some-image.bb should control what gets into image? (i guess this should be preferred?). On one hand - if you include a layer this could "push" itself into image, on the other,
<Guest45>
specific image recipe could control better what gets inside. Let's assume this software i'd like to be included pretty much to every image, qemu or normal image
<Guest45>
2. Should one prefer setting TEMPLATECONF instead of providing whole conf directory with bblayers.conf.sample and/or layers.conf.sample? I see this being done by some OEMs. They seem to use poky as distro, or at least use oe-init-build-env from poky, but doing some sort of heuristic should build dir be reused or not... wait I've just read what i
<Guest45>
wrote in (2), and let me rephrase, i don't understand what i wrote myself ;)
<Guest45>
If one wants to roll own distro, without relying (too-much-) on poky, what are the choices?
<Guest45>
- copy oe-init-build-env
<Guest45>
- use oe-core init
<Guest45>
- simply create & copy conf dir with bblayers.conf & local.conf
<Guest45>
3. actually last one - while i feel it would be quite wrong thing to do to commit build/conf directory - i sort of wonder sometimes why. Yes, separate layers, configs, distro.conf image definitions - are separating things better.
<Guest45>
but if one assumes that distro and its config is supposed to be created once, and rarely updated, what is the real benefit here? Wouldn't navigating build/conf/local.conf with all real configs "merged" into one, more convenient and ultimately "easier" (that is - without the need to check what might have had overwritten some settings?). Imagine:
<Guest45>
distro.conf defines some defaults, layer X changes some, image_z.bb changes some others, machine.conf can change some other... i know there are plenty of mechanisms inside yocto to track those, but somehow it seems more complicated if one doesn't work with yocto every day for months...
ehussain has joined #yocto
sgw has quit [Ping timeout: 245 seconds]
ptsneves has joined #yocto
sgw has joined #yocto
ptsneves has quit [Ping timeout: 252 seconds]
druppy has joined #yocto
frgo has quit [Remote host closed the connection]
frgo has joined #yocto
druppy has quit [Client Quit]
druppy has joined #yocto
druppy has quit [Ping timeout: 246 seconds]
druppy has joined #yocto
florian_kc has joined #yocto
druppy has quit [Ping timeout: 246 seconds]
reatmon_ has quit [Remote host closed the connection]
reatmon_ has joined #yocto
Kubu_work has joined #yocto
Kubu_work has quit [Client Quit]
sanbeam9 has joined #yocto
sanbeam18 has joined #yocto
sanbeam9 has quit [Ping timeout: 248 seconds]
sanbeam has joined #yocto
sanbeam18 has quit [Ping timeout: 248 seconds]
ehussain has quit [Remote host closed the connection]
Abp has quit [Ping timeout: 245 seconds]
Abp has joined #yocto
goliath has joined #yocto
uglyoldbob has quit [Quit: Client closed]
Abp has quit [Read error: Connection reset by peer]
Abp has joined #yocto
florian_kc has quit [Ping timeout: 265 seconds]
paulg has joined #yocto
sanbeam9 has joined #yocto
<kanavin>
Guest45, I'm not sure what is the question you are asking tbh. Maybe you should write an email to yocto list?
<kanavin>
I guess what I could say is that a) making own image recipes is preferred; b) making own configuration templates (conf/templates/templatename) is preferred as well.
Abp has quit [Read error: Connection reset by peer]
Abp has joined #yocto
sanbeam18 has joined #yocto
sgw has joined #yocto
sanbeam9 has joined #yocto
sanbeam18 has quit [Ping timeout: 276 seconds]
sakoman has quit [Ping timeout: 248 seconds]
sakoman has joined #yocto
Guest45 has joined #yocto
sotaoverride has joined #yocto
ptsneves has joined #yocto
<Guest45>
Hi kanavin, thx for the answer. Sorry for being perhaps not clear enough. My 1st question could be perhaps shortened to:
<Guest45>
1. if i have own image, is it rather preferred for the image to define what should it pull from various layers, or rather layer would push (by appending to core image) newly added items from itself (the layer), into image?
<Guest45>
2. i guess there are no downsides to using poky's oe-init + providing templateconf, as opposed to seen here and there pattern of copying whole conf dir (or even oe-init script + conf dir) done by some OEMs
ptsneves has quit [Ping timeout: 248 seconds]
sanbeam18 has joined #yocto
geoffhp has quit [Ping timeout: 252 seconds]
sanbeam9 has quit [Ping timeout: 248 seconds]
sanbeam9 has joined #yocto
sanbeam18 has quit [Ping timeout: 260 seconds]
florian_kc has joined #yocto
Guest46 has joined #yocto
Guest46 has quit [Client Quit]
florian_kc has quit [Ping timeout: 245 seconds]
nerdboy has quit [Ping timeout: 252 seconds]
steelswords9436 has quit [Read error: Connection reset by peer]