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

Add Cliver::detect #2

Closed
yaauie opened this issue Jun 28, 2013 · 0 comments
Closed

Add Cliver::detect #2

yaauie opened this issue Jun 28, 2013 · 0 comments

Comments

@yaauie
Copy link
Owner

yaauie commented Jun 28, 2013

WIP notes

Sometimes just making sure that the first executable on your path is the right version isn't enough; we should be able to look for an executable that satisfies the requirements, not just make sure that the first one on the path is ok. A perfect example of this is python, with the 2/3 split, where many users must have both installed.

The interface should be pretty similar to the existing Cliver::assert, but should have an explicit return value of the full path to the executable. If no appropriate executable can be detected, this will raise like Cliver::assert does, except that the message needs to have information about many found-and-not-good-enough binaries.

executable_path = Cliver::detect(executable, *requirements, options = {})
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant