2048.c conflicts with 2048.cpp

[barracuda156]

Error: Failed to activate 2048.cpp: Image error: /opt/local/bin/2048 is being used by the active 2048.c port.  Please deactivate this port first, or use 'port -f activate 2048.cpp' to force the activation.
    while executing
"throw registry::image-error $msg"
    ("foreach" body line 49)
    invoked from within
"foreach file $imagefiles {
                incr progress_step
                _progress update $progress_step $progress_total_steps
                se..."
    invoked from within
"registry::write {
            # extract phase complete, assume 1/3 is done
            set progress_step $num_imagefiles
            foreach file $ima..."

[TheRealKeto (Keto)]

Unsure on how this should be resolved. I have 2 ideas

1. Make these ports co-exist by adapting them to semantic naming (e.g Homebrew used c2048 to name the formula equivalent to this port), like cpp2048 or 2048cpp, or

2. Use the conflict field for these ports and not worry

[barracuda156]

Replying to TheRealKeto:

Unsure on how this should be resolved. I have 2 ideas

1. Make these ports co-exist by adapting them to semantic naming (e.g Homebrew used c2048 to name the formula equivalent to this port), like cpp2048 or 2048cpp, or

2. Use the conflict field for these ports and not worry

It is a simple one-binary port, perhaps rename is preferable, why introduce unnecessary conflict.

[TheRealKeto (Keto)]

In 38c6f380ef6cca0f61b8c54405b6525881e9b32b/macports-ports (master):

2048.c: Fix conflicts with 2048.cpp

Closes: #69946