You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding the whole repo to the path (as per the installation instructions) litters the path with many binaries that have names that are seeminlgy unrelated to git-radar.
fetch.sh
radar-base.sh
test-branches.sh
test-colors.sh
test-commits.sh
test-directories.sh
test-files.sh
test-format-config.sh
test-performance.sh
test-radar-base.sh
test-stash.sh
test-status.sh
It would be nice if this could be changed so git-radar only adds a single binary to the path, or at least if the scripts are renamed so it's obvious that they belong to git-radar. i.e. git-radar-fetch.sh
Following UNIX convention (e.g. hier(7)), binaries executed by the user (only git-radar here) should be installed to $prefix/bin, whilst the helpers executed by that binary go in $prefix/libexec.
Putting only git-radar in /bin and the source scripts in /libexec is exactly what the homebrew release does. Since I was on OSX it was the only release process I really cared about / was able to properly dogfood.
I'm now on Ubuntu as my daily driver and in need of finding a better release approach for linux. FPM seems the way to go.
So the outcome of all this is:
Yeah, I agree. I'm looking in to it and would like to fix it soon.
Adding the whole repo to the path (as per the installation instructions) litters the path with many binaries that have names that are seeminlgy unrelated to git-radar.
fetch.sh
radar-base.sh
test-branches.sh
test-colors.sh
test-commits.sh
test-directories.sh
test-files.sh
test-format-config.sh
test-performance.sh
test-radar-base.sh
test-stash.sh
test-status.sh
It would be nice if this could be changed so git-radar only adds a single binary to the path, or at least if the scripts are renamed so it's obvious that they belong to git-radar. i.e.
git-radar-fetch.sh
Possibly related to #51 #10
The text was updated successfully, but these errors were encountered: