16:36 <LetoThe2nd> rbox: "not compiling it at all" is probably a problem if its required at build time.

17:03 <rbox> LetoThe2nd: i wound up creating a dummy update-alternatives package, but opkg-utils-native still gets compiled, that's the one needed at build time

17:04 <rbox> I found myself modifying a receipes PACKAGES variable in my local.conf for a few others, on a scale of 1 to 10, how bad is that?

17:06 <LetoThe2nd> rbox: I would give it a 9.9993

17:06 <rbox> haha

17:09 <rbox> if they didnt want me to do it, they shoudln't have given me the ability

17:09 <rbox> haha

17:40 <rbox> is there anything that actually explains what POKY_BBLAYERS_CONF_VERSION

17:44 <simonew> are there issues with sstate? I see the object check taking very long

21:17 <AdrianF> rbox: Could removing the package-management feature from IMAGE_FEATURES be what you are looking for? See https://docs.yoctoproject.org/ref-manual/features.html?highlight=image+features#image-features.

21:17 <rbox> no

21:20 <AdrianF> This one: https://docs.yoctoproject.org/ref-manual/variables.html?highlight=unneeded#term-FORCE_RO_REMOVE?

21:20 <rbox> i dont want to build them

21:21 <rbox> not r emove them

21:21 <Saur_Home39> What's the problem with building them?

21:21 <rbox> i dont want to?

21:21 <rbox> lol

21:26 <Saur_Home> Well, there is a lot being built for target that I know will never be used in our products, like perl, bash, etc. However, trying to avoid it is a lot of work for very little gain. The way OE works means that a lot of things are built since some package somewhere has a dependency on it, and it is not until an image is actually created that it is

21:26 <Saur_Home> known if what was built will be used.

21:29 <rbox> yeah, i've gathered that

21:30 <rbox> futzing with PACKAGES and DEPENDS and stuff seems to do wahat i want, even though ti seems a bit messy