-
Notifications
You must be signed in to change notification settings - Fork 55
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
remove general include of REXML #32
Conversation
this fixes thias#31 where the provider fails on CentOS 6.5 (probably on older ruby versions in general)
would be pretty cool if we head beaker tests for this module ;) |
Probably, but I'm sorry - I can't build those. I can just say that I tested it on CentOS 6.5 and it works for me and it's the only instantiation of a REXML class in the whole file. There's no conceivable reason it should not work on any other ruby either. |
I applaud your optimism :| |
I'll submit a pr for beaker testing, but I just realized we don't have any |
I agree that tests are always better, but in this case I'll stick with my optimism. There's no other file including the changed file and the type itself doesn't use REXML at all. I'll give a little bit of ruby education here: You probably never want to use
If some other part of the code tries to use a constant named |
Actually, maybe this code would work (not tested, depends on the puppet implementation of
But the initially proposed change is "nicer" ruby since it avoids including REXML completely. |
You'll probably want to do the same change in #25 though :) |
I'm confuzzled. I thought ruby modules always have global scope. |
ack, thanks. Re-reading this, I think I get it now. |
ok :) Feel free to ask via PM or email if you have ruby questions, since probably this is probably not the right place. If you're interested I'll go over the ruby code and do some style criticism, but I'd move that to a different PR. |
I think that criticism should be moved over to #25 ;) |
Thanks! Applying many changes... re-created as 7d3e0bd. |
this fixes #31 where the provider fails on CentOS 6.5 (probably on older ruby versions in general)