Script tests tied to interpreter
Reported by bahuvrihi | February 16th, 2009 @ 12:01 AM
Command paths like:
def default_command_path
%Q{ruby #{LOAD_PATHS} "#{RAP_EXECUTABLE_PATH}"}
end
Have the effect of tying a script test to a particular ruby interpreter... not what you want. The interpreter may need to be determined dynamically, or, maybe a whole new solution is needed. After all, this presupposes a developer calls 'ruby' in the first place.
Currently affects (in tap):
- generator_test
- run_test
- tap_test
- readme_test
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
A framework for making configurable, file-based tasks and workflows.
bahuvrihi