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

Detect Ruby implementation version and noop unless appropriate #17

Open
ivar opened this issue Jun 21, 2011 · 2 comments
Open

Detect Ruby implementation version and noop unless appropriate #17

ivar opened this issue Jun 21, 2011 · 2 comments

Comments

@ivar
Copy link

ivar commented Jun 21, 2011

Since the SystemTimer gem is admittedly a hack (though a very useful and appreciated hack) to work around implementation issues for a limited subset of ruby implementations (ie: 1.8.x), it would be great if the gem could detect the current environment in which is it is running and only take effect when appropriate. This would would allow otherwise compatible gems to run successfully in other environments (ie: Ruby 1.9, jruby, etc..).

see also #10

@zimbatm
Copy link

zimbatm commented Jul 4, 2011

If you use a Gemfile, you can target a dependency for ruby 1.8 only like that:

gem 'SystemTimer', :platforms => :mri_18

@ivar
Copy link
Author

ivar commented Jul 4, 2011

see rubygems/bundler#1281

apparently, the 'official' solution is to create a different gem version for each platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants