git-radar icon indicating copy to clipboard operation
git-radar copied to clipboard

Published 20 hours ago • verified publisher icon michaeldfallen

Reduce the number of binaries needed to be added to the path

Open johanhelsing opened this issue 9 years ago • 3 comments

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

johanhelsing avatar Dec 30 '15 14:12 johanhelsing

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.

srstevenson avatar Dec 30 '15 17:12 srstevenson

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.

Sorry that's not more helpful.

michaeldfallen avatar Jan 13 '16 11:01 michaeldfallen

It's worth mentioning that /usr/libexec is now merged with /usr/lib on most distros.

djmattyg007 avatar Mar 01 '17 20:03 djmattyg007