//google-cloud-sdk:PKGBUILD should pick a singular location for executables
sudoforge opened this issue · comments
The
PKGBUILD
could be refactored to remove this block altogether, and the package would still work as expected. This is something that should happen, but hasn't been a priority as it won't actually change the package in any meaningful way.
Originally posted by @sudoforge in #18 (comment)
We should clean up the block that creates some symlinks in /usr/bin
(or, conversely, remove the need for /opt/google-cloud-sdk/bin
to be in PATH
). This creates a divide in the "real" path to executables, as is confusing to new users (see #18).
Are we only adding /opt/google-cloud-sdk/bin
to PATH
via google-cloud-sdk.sh
in order to add the executables which aren't symlinked to /usr/bin
? If so, we should probably prefer creating symlinks (if this is necessary) for all executables to /usr/bin
, and removing the PATH
extension from google-cloud-sdk.sh
.