mc: conflicts with mc

https://github.com/minio/mc/blob/master/CONFLICT.md - this has been documented here and how to mitigate this problem.

How about minc? I kind of like it better actually because it makes me think of Minks.

It doesn't matter what you name the binary locally for your purposes.

@silvernode :
We would like to close this issue as working as intended since this is a small collision and you can always rename Minio Client (mc) whatever the way you'd like.
Please let us know if you are OK with it. Thanks...

Well I would suggest another name just for the sake of clarity, although it's your project and you can do what you wish. The fact that Midnight Commander has existed since the beginning of Linux makes me feel like it should get to claim "mc" as it's command name. Maybe only old time Linux users will understand where I am coming from. Midnight Commander is such a timeless application and I don't think anyone should have to bother renaming minio. This is exactly why namespaces and trademarks exist. Just my 2 cents, you can close this issue any time you wish.

Minio Client as mc is project which creates a single statically compiled executable binary which can be placed anywhere (by any name) in the system for user convenience.

When distributing mc's executable, package maintainer could choose convenient name which works for the system. We encourage this. Package maintainers are already doing it e.g. Ubuntu snap is called as minio-client.

Hope this helps.

Wow, this is already the third ticket about the same ticket. Let's fight unemployment and create work by creating confusion. Dear minio creators: please think about this again. If you want mc then you can create an alias for you. I think the current name conflict can only be solved by minio devs by choosing a different name.

@guettli the ship has sailed on that, mc will remain as mc.