Closed QSchulz closed 1 year ago
If it breaks it's because they forgot to add the appropriate native dependencies in their recipes, in which case it is a good thing that it does. Also might highlight dependencies of Yocto that are missing in the docs.
Not sure exactly what's the issue with possibly breaking users? Am I missing something or do we just have a different opinion on the topic :)?
Ya, I'm just leery of making a pyrex upgrade suddenly break someones build (even if it is due to a misconfiguration on their end). Smaller images are nice, but I'm not sure it's worth breaking someones existing workflow to do it. When we make a new image (Ubuntu 22.04 for example) that makes more sense since it's more of an opt-in thing to switch to that image.
Do you really want an MR for just a comment or do we just keep this one open as a reminder til we get to 22.04 :) ?
Do you really want an MR for just a comment or do we just keep this one open as a reminder til we get to 22.04 :) ?
I have no preference.
I believe this is taken care of in the new Ubuntu 22.04 in #81. Please check that and close this
Yup, the diff looks like what I'd have expected 🎉
14.04 is 12% smaller, 16.04 7%, 18.04 10% and 20.04 3%.
This was not tested (only built with:
podman build -t 14.04-oe -f image/Dockerfile --build-arg PYREX_BASE=ubuntu-14.04-oe --target pyrex-oe
).