On 17/06/2024 13.43, Alexander Kanavin wrote: > This then needs to happen for all of the core system executables,
No, that's not at all true, and does not follow logically. > not just these three ones you happen to be using. [I happen to need just one, that's the point.] > Packaging should > follow a policy and not be an inconsistent mishmash. But having a policy > that splits every executable into its own package would be a maintenance > nightmare. I really don't see how this is any different from any of the dozens of the existing recipes that show up if you do "git grep 'FILES.*bindir'". iproute2, e2fsprogs, psmisc, openssh, mtd-utils and lots of others package binaries in distinct packages (not necessarily one-executable-per-package, e.g. mtd-utils collects the ubifs and jffs2 related ones). > I’d say this should stay in a private layer if you really don’t want to > just use busybox. I already explained why relying on busybox providing the necessary applet with the necessary features is the inferior option. I also provided additional arguments for why allowing one to install, say, xargs, without pulling in the locate binary, might be desirable. Rasmus
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#200834): https://lists.openembedded.org/g/openembedded-core/message/200834 Mute This Topic: https://lists.openembedded.org/mt/106717870/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
