Greetings! After watching a talk from Michael Opdenacker from this year's OSS Europe about Yocto Binary Distros (see [1]), I've been experimenting with installing pre-built packages directly onto the target and I have a few questions regarding this topic, maybe someone more experienced could chime in:
1) When I build a recipe previously not installed in my image and want to install it during runtime, the dnf install command fails, saying that the package's dependencies are not met (see [2] for more info). This is fine, as I can see that the tmp/deploy/rpm directory does not contain all of the package's dependencies nor the dependencies' WORKDIRs contain the deploy-rpms directory. Is this behavior correct? Shouldn't building a recipe also lead that all of its dependencies are not just built but also packaged and put into the tpm/deploy/rpm directory (the same as with building the image containing the package in question)? 2) Is there an official, stable, and not some hacky way to install already pre-built packages during the build and not later during runtime? So instead of building from source or from the sstate-cache, to provide a URL to a webserver holding packages, which would then be pulled and installed (if I am not wrong Isar does this)? 3) Is enabling and using the package runtime management recommended and encouraged when it comes to Yocto running on actual devices and not during a development phase? IMHO we are talking about embedded devices here, with little or no user interaction, with secure boot enabled, atomic updates, etc. and having a package management system such as dnf or apt is cool, but is also kind of brittle (a simple power off during apt update can break the system). Thanks. Aleksandar [1] Building and Maintaining Binary Distributions with Yocto - Michael Opdenacker, Root Commit - YouTube ( https://www.youtube.com/watch?v=UdJZ0xz-QLk&list=PLbzoR-pLrL6rC7SpO7MJCZm22Qp5ns3p-&index=66 ) [2] # building the image bitbake core-image-minimal bitbake package-index # building the recipe which is not in the image bitbake vim bitbake package-index # trying to install the recipe in core-image-minimal fails root@qemux86-64:~# dnf install vim OE Remote Repo: rpm core2_64 970 kB/s | 476 kB 00:00 OE Remote Repo: rpm qemux86_64 238 kB/s | 62 kB 00:00 Error: Problem: conflicting requests - nothing provides libXt.so.6()(64bit) needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 - nothing provides libgdk-3.so.0()(64bit) needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 - nothing provides libgdk_pixbuf-2.0.so.0()(64bit) needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 - nothing provides libgtk-3.so.0()(64bit) needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 - nothing provides libpango-1.0.so.0()(64bit) needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 - nothing provides libpangocairo-1.0.so.0()(64bit) needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 - nothing provides libgdk-pixbuf-2.0-0 >= 2.42.12 needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 - nothing provides libgtk-3.0 >= 3.24.43 needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 - nothing provides libxt6 >= 1.3.0 needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 - nothing provides pango >= 1.54.0 needed by vim-9.1.0698-r0.core2_64 from oe-remote-repo-rpm-core2_64 (try to add '--skip-broken' to skip uninstallable packages)
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63944): https://lists.yoctoproject.org/g/yocto/message/63944 Mute This Topic: https://lists.yoctoproject.org/mt/108862936/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
