Look for gnu-coreutils commands instead of $OSTYPE

[ColinHebert]

It's possible to have the gnu-coreutils on other environments than Linux

[sorin-ionescu]

What does dircolors have to do with du?

[ColinHebert]

dircolors isn't defined in BSD-coreutils (AFAIK it's a GNU-coreutils specificity), so this allows to quickly check which coreutils is available. (I haven't tried any other form of coreutils yet).

But du is defined in every coreutils, so there are two solutions, either try to call du with the wrong options and catch the potential errors or trust dircolors.

[sorin-ionescu]

(( $+commands[dircolors] )) won't work anyway since it will be wrapped in a function in the case of the gnu-utils module. We need a more reliable way to detect GNU core utilities.

[sorin-ionescu]

There is a _pick_variant function in the man page.

[sorin-ionescu]

There is also grep -q -i GNU < <(du --version 2>&1).

[ColinHebert]

I've seen a lot of attempts to define which version of coreutils is used. One of them is with strings on the executable, eg strings du contains the "GNU coreutils" string

[sorin-ionescu]

grep -q -i GNU < <(strings $(type -p du | cut -d' ' -f3-)) won't work with gnu-utility.

[ColinHebert]

whence -p should give a better result than type -p (no need to cut it). But anyway, it doesn't help, we don't need the -p because it's not a file accessible in a path, it's a function.