On Sat, 10 Oct 2026 at 13:30, Etienne Cordonnier via lists.openembedded.org <[email protected]> wrote:
> > uutils-coreutils, the Rust reimplementation of GNU coreutils, is mature > enough for production use, so move the recipe from meta-oe to oe-core. > It provides and rprovides coreutils, and is excluded from world unless > selected as the coreutils provider. > This needs a bit more justification. What is achieved by moving it to core? What specifically makes this component mature enough? What tests were performed with it? Does it pass the full autobuilder matrix when selected as coreutiuls provider? Should we add that test to the autobuilder? Should we make uutils-coreutils the default choice, or maybe the only choice? Does it work as a provider of coreutils-native, and is it compatible with pseudo? Adding things to core has a pretty high bar, and the above commit message does not meet it. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#247643): https://lists.openembedded.org/g/openembedded-core/message/247643 Mute This Topic: https://lists.openembedded.org/mt/121685421/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
