Use RbConfig instead of obsolute and deprecated Config when defined

[joshaven]

This will use RbConfig but will fallback to Config if RbConfig is not defined

[kevinburke]

This project is no longer maintained. I've merged the above fix to my fork
observr: http://github.com/kevinburke/observr

Kevin Burke
phone: 925.271.7005 | kev.inburke.com

On Fri, May 23, 2014 at 8:21 AM, Joshaven Potter
[email protected]:

This will use RbConfig but will fallback to Config if RbConfig is not

defined

You can merge this Pull Request by running

git pull https://github.com/joshaven/watchr master

Or view, comment on, or merge it at:

#55
Commit Summary

• Use RbConfig instead of obsolute and deprecated Config when defined

File Changes

• M Rakefile https://github.com/mynyml/watchr/pull/55/files#diff-0(3)
• M lib/watchr.rbhttps://github.com/Use RbConfig instead of obsolute and deprecated Config when defined #55/files#diff-1(3)

Patch Links:

• https://github.com/mynyml/watchr/pull/55.patch
• https://github.com/mynyml/watchr/pull/55.diff

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/55
.

[DavidEGrayson]

Are there any forks of watchr that still maintain the same interface/usage? The problem with the observr gem is that you have to type observr on the command line instead of watchr. I would rather keep using the watchr command. In general, the users of open source software should not have to adapt to a new interface for using the software just because someone stopped maintaining the software. There should be forks that still maintain the same interface.

I would like to see a gem with name like watchr-xyz that provides the exact same interface, where "xyz" are the initials of the new person or group that stepped up to maintain it. Then the next time watchr goes into disrepair, all we have to do is update our Gemfiles to point to a new fork, and we don't need to change our habits and scripts.