Hi Markus, When I tried running puppetd --debug --verbose --trace after making changes for const_defined? without changing File, I ran into some stack traces regarding no method error for File which made me suspect that somehow Ruby 1.9.x changed some of the behavior for searching for constants in moduled namespaces. When I add the double colons to explicitly tell File to use the top-level File object instead of possibly being confused with Puppet::Type::File these warnings went away.
Frankly, I would rather not change it but I am not sure if this is something with the way the code is implemented that does not work with Ruby 1.9.x or this should be brought up with the Ruby core team. If there is a better way to handle this, I would be willing to try it. Alain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
