gdu conflicts with coreutils

[neverpanic (Clemens Lang)]

$ sudo port activate gdu
--->  Activating gdu @5.13.0_0
Error: Failed to activate gdu: Image error: /opt/local/bin/gdu is being used by the active coreutils port.  Please deactivate this port first, or use 'port -f activate gdu' to force the activation.
    while executing
"throw registry::image-error $msg"
    ("foreach" body line 47)
    invoked from within
"foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to install links, we test if we can lst..."
    invoked from within
"registry::write {
            foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to instal..."
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_gdu-5.13.0_0_dc05bfe7584af9d0740eb577b7b5bbd62737dab1be80a65be65278b61a57da21-8754/gdu/main.log for details.
Warning: Failed to execute portfile from registry for gdu @5.13.0_0

corutils installs its tools with a 'g' prefix (for GNU), and the gdu port attempts to install the same binary. I'd like to have both installed. Can we find a way to make this happen?

If not, gdu and coreutils should at least use the conflicts keyword.

[mascguy (Christopher Nielsen)]

Perhaps the gdu binary could be renamed to something like gdu-go? (And call out the binary name in the port notes, to avoid user confusion.)

[herbygillot (Herby Gillot)]

In 1f47c9952d997ae6e6dc4774671be6525dfb34b1/macports-ports (master):

gdu: rename executable & man page to avoid conflict with coreutils

Fixes: #64578

[neverpanic (Clemens Lang)]

Thanks!