Re: [NEW] sysutils/uutils

www.mail-archive.com · 2026-09-30 · by Long Nguyen ·generic

Re: [NEW] sysutils/uutils

[Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/search?l=ports@openbsd.org&q=subject:%22Re%5C%3A+%5C%5BNEW%5C%5D+sysutils%5C%2Fuutils%22&o=newest)

Theo de Raadt Sun, 20 Sep 2026 12:03:20 -0700

David Uhden Collado <[[email protected]](https://www.mail-archive.com/cdn-cgi/l/email-protection)> wrote:

Stuart Henderson wrote:
> On 2026/09/20 07:01, David Uhden Collado wrote:
>> The main goal of the packaging is to make these implementations usable
>> as alternatives to the existing GNU utility ports without requiring
>> source changes in dependent ports.
>>
>> For example, uutils-coreutils installs the same g-prefixed command names
>> as sysutils/coreutils, including gcat, gls, gcp, gdate, gsort, gstat,
>> gtail, gtimeout and the other GNU-compatible utilities. They are
>> symlinks to the upstream multicall binary, which is installed under
>> libexec/uutils.
> ...
>> Each package conflicts with its corresponding GNU implementation and
>> declares the GNU port as a secondary @pkgpath.
> I don't think this is a usable approach for ports.
>
The truth is, I find these Rust reimplementations quite
interesting. Ubuntu 26.10 has already adopted uutils coreutils because
the project has reached a level of maturity and stability where it can
be used reliably. The other reimplementations are still more of a work
in progress.

Smells like agenda.

I also think they fit quite well with OpenBSD as alternatives to GNU
utilities, particularly because they use a permissive MIT license.

Argument is vaguely like: because we already have permissive licenced utilities, our user base are really interested in having a second set of permissive licenced utilities which are very subtly different.

That makes no sense. Noone wants subtly different behaving binaries as part of their workflow. If someone runs the openbsd ls command as part of a pipeline that uses openbsd sed, or openbsd cut, or some other openbsd utility and it parses a non-standized output characteristic by accident, there are no people in this universe who wants to replace that ls with a different ls and get surprised by un-standardized tooling behaviour clash.

I'm not sure yet whether it's possible to install the individual
utilities as separate binaries. This is new territory for me, since
uutils is structured as a metapackage, and because it's written in
Rust.

Oh, because it is written in Rust. Your agenda is showing.

[Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143879.html) Stuart Henderson [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143891.html) David Uhden Collado Re: \[NEW\] sysutils/uutils Theo de Raadt [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143893.html) David Uhden Collado [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143894.html) Theo de Raadt [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143895.html) David Uhden Collado * [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143897.html) Stuart Henderson [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143900.html) Theo de Raadt [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143934.html) Stuart Henderson * [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143898.html) Antoine Jacoutot [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143902.html) David Uhden Collado [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143905.html) Stuart Lamble * [Re: \[NEW\] sysutils/uutils](https://www.mail-archive.com/ports@openbsd.org/msg143996.html) Anthony J. Bentley

Reply via email to

www.mail-archive.com · 1 images · 27 links

Comments (0)

No comments yet