From: Collin Funk <collin.funk1@gmail.com>
To: Etienne Cordonnier <ecordonnier@snap.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] uutils-coreutils: move from meta-openembedded
Date: Mon, 12 Oct 2026 15:58:42 -0700 [thread overview]
Message-ID: <m11p9u4jbx.fsf@gmail.com> (raw)
In-Reply-To: <CAHUKmYZOUvohA9psyEiJ251a9mCnTteUDkdAVU1LEAAFC_PdZw@mail.gmail.com>
Etienne Cordonnier <ecordonnier@snap.com> said:
> - what is achieved by moving it to core is improving no-gplv3.inc for users
> who are not using gplv3 and still want full coreutils syntax support. It
> will also make it possible to add it to poky-altcfg.conf, and generally
> make it easier to consume without needing meta-openembedded.
That, of course, assumes none of the code is tainted after the attempted
cleanup in 0.12.0, which only came after multiple warnings from me. It
is difficult, speaking personally, for me to believe that the uutils
project has any respect at all for licensing.
> - its adoption in Ubuntu 26.04 as default coreutils implementation and
> the resulting large-scale usage and bug-fixing
That is the positive side of things. The negative side is that there
were many FTBFS and multiple breakages of Ubuntu ISOs. E.g., one missing
a setuid bit on sudo. I highly doubt Canonical engineers enjoy dealing
with this. It seems to be a decision made by the company leadership. I
can't say for certain, though, since Canonical didn't reach out to me or
anyone else working on GNU coreutils, who could have warned them about
the easily foreseeable issues they faced.
> - its >95% pass-rate of the GNU testing suite in release 0.0.12 (some
> tests are still skipped)
Note that the GNU coreutils test suite is good, in my biased opinion,
but it is not really meant to create a new, perfectly compatible
implementation to replace us. I have always found the use of these
percentages dubious, but I understand the need for some comparison.
> Also rust binaries are bigger than C binaries so there is some
> tradeoff involved. GNU coreutils 9.12 main package is 10.3MB big in my
> test build, compared to 13.6MB for the uutils-coreutils 0.0.12 main
> package (uutils-coreutils uses a multi-binary executable to save
> space, GNU coreutils doesn't).
This is a very unfair comparison. GNU coreutils has been able to be
built as a single binary since 2014 [1]. If there were a need for it in
meta-openembedded, I am sure it could be packaged relatively easily. Red
Hat uses it for their container images, for example:
$ podman run --rm -it redhat/ubi10
$ du --human-readable /bin/coreutils
1.4M /bin/coreutils
Collin
[1] https://github.com/coreutils/coreutils/commit/71e2ea773414b2316bbe6b803b9a52c38d3752e8
next prev parent reply other threads:[~2026-10-13 2:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 11:30 [PATCH] uutils-coreutils: move from meta-openembedded ecordonnier
2026-10-10 18:33 ` Collin Funk
2026-10-11 16:23 ` [OE-core] " Yoann Congal
2026-10-12 13:04 ` Alexander Kanavin
2026-10-12 21:13 ` Etienne Cordonnier
2026-10-12 22:58 ` Collin Funk [this message]
2026-10-13 7:41 ` Alexander Kanavin
2026-10-13 8:13 ` Yoann Congal
2026-10-13 10:02 ` Etienne Cordonnier
2026-10-13 10:24 ` Alexander Kanavin
2026-10-13 10:54 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m11p9u4jbx.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=ecordonnier@snap.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.