> The only gotcha I've found are a couple of versions of Puppet (2.7.20+ > and 3.0.x) which don't load custom types from lib/ in the module, so > there's a workaround in the above file.
This seemingly innocuous statement has cleared up for me the problem of being unable to require, from my custom types and providers, sundry Ruby modules I wrote. I thought Puppet wouldn't let me use my own Ruby modules at all, and now to my great relief I see I was quite wrong. The other things you've said about the spec helper are also very helpful and complete. Thanks very much! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
