Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fix #7] Use the libexec/ directory rather than bin/ for internal commands #21

Merged
merged 3 commits into from Dec 27, 2014

Conversation

jfarmer
Copy link
Contributor

@jfarmer jfarmer commented Dec 21, 2014

By convention, libexec/ is used for binaries not meant to be executed directly by a user. This convention is "codified" in the Filesystem Hierarchy Standard. I learned this after investigating where and how git places its own internal commands, e.g., git-add, git-commit, git-config, etc.

This requires modifying ENV["PATH"] in the bin/codeunion executable and fixes issue #7 (brew doctor complaining about codeunion-config being in the user's PATH).

Per the "Filesystem Hierarchy Standard", libexec/ is meant for binaries that
are not meant to be executed by other programs.  This is where git stores all
of its internal commands, e.g., git-add, git-commit, git-config, etc.

This will fix the issue of `brew doctor` complaining about codeunion-config.
Currently the feature test for `codeunion-config` executes
`bin/codeunion-config` directly. Rather than changing the
test to execute `libexec/codeunion-config`, just use the
user-facing interface: "codeunion config [OPTIONS]".
@zspencer
Copy link
Contributor

👍 🎉 :shipit:

zspencer added a commit that referenced this pull request Dec 27, 2014
…l-commands

[Fix #7] Use the `libexec/` directory rather than `bin/` for internal commands
@zspencer zspencer merged commit c4731dd into master Dec 27, 2014
@zspencer zspencer deleted the jfarmer/use-libexec-for-internal-commands branch January 2, 2015 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants