Marco d'Itri <m...@linux.it> writes: > On Apr 21, Mathias Gibbens <gib...@debian.org> wrote: > >> While that might work for them, it obviously doesn't at a higher >> packaging level. Per Policy Section 10.1, I'm bringing this to d-devel >> for any comments or suggestions on my plan for packaging the MinIO >> Client. Following what several other distributions have done[2], I'm >> planning to name the source/binary packages "minio-client" and the >> binary provided from that package will be `mcli`.
+1 > Go for it, I think that there is no good solution for this case. > Everybody who cares then will manually create a mc -> mcli symlink. Several Homebrew packages uses an approach that I regard as superior to what the debian ecosystem provides for this problem: putting files in a path that users can add to their $PATH to get upstreams' desired binary name, when there is a conflict with a historically established name. So for this example, minio-client could create a symlink like this /usr/libexec/minio-client/bin/mc -> /usr/bin/mcli and users who really want the upstream behaviour can solve this by modifying environment variables. /Simon
signature.asc
Description: PGP signature
