3 ms·
FWIW we recently started using the Yocto-based BalenaOS[0] in our project and have been rather happy with it because we get to focus on developing and running o
by codethief 6y ago
FWIW we recently started using the Yocto-based BalenaOS[0] in our project and have been rather happy with it because we get to focus on developing and running our software and don't have to bother with the low-level hardware stuff too much.
Unfortunately, as we're getting closer to shipping our product, we've realized that Balena seems to be rather cavalier when it comes to respecting software licenses. They offer pre-built .img files and Docker base images but don't provide a comprehensive list of licenses (let alone the source code) of third-party software components anywhere, as this issue[1] attests to. I'm currently talking to one of their customer service representatives and, as of this morning (when they sent me another email), they don't even acknowledge that this is an issue.
Looks like we'll now have to compile this list on our own. :\
[0]: https://www.balena.io/os https://www.balena.io/os
[1]: https://github.com/balena-os/meta-balena/issues/1955 https://github.com/balena-os/meta-balena/issues/1955
- ephaeton 6y agoI don't know BalenaOS, but if it's yocto based, using this bbclass might help you out: https://gist.github.com/weber-martin/fa9ca5bdceffc9504175f6e629571f06 https://gist.github.com/weber-martin/fa9ca5bdceffc9504175f6e... add "extra_license" to your IMAGE_CLASSES_append in your (machine, distro) config. add EXTRA_COPY_LIC_ROOTFS = "1" to your liking. You will end up with a directory of licenses, including license texts, of the packages you have in your image. Yeah you will have to build your image yourself, but isn't that $trivial with yocto (FSVO $trivial ?)
- codethief 6y agoThanks so much, I will look into this! :)