Hi, here from Serpent/Aeryn. By this point I've fixed a bunch of packages that had incompatibility with uutils-coreutils and one thing I've consistently noticed is that many packages parse --version in order to identify what is providing a given binary. Coreutils/busybox all have something in that output to identify them as such, however it looks like uutils versions only output the command name plus the version string (likely due to .version(crate_version!())).

Example coreutils output:

> mkdir --version
mkdir (GNU coreutils) 9.5
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

Uutils mkdir output:

> mkdir --version
mkdir 0.0.29

Usually I have to create a downstream patch for the package that just skips the check and forces it to be equivalent to whatever coreutils supports, but if there was a uutils-specific identifier in this output I could be creating an upstreamable patch instead.

Something like this would be ideal:

> mkdir --version
mkdir (uutils-coreutils) 0.0.29

For example, here is some version parsing logic that I had to patch around recently:

       case `"$as_dir$ac_prog$ac_exec_ext" --version 2>&1` in #(
         'mkdir ('*'coreutils) '* | \
         'BusyBox '* | \
         'mkdir (fileutils) '4.1*)