> Agree, I should take advantage of autoloader, but how people handle > those classes where the implementation of multiple modules are required?
I don't understand this question. More context needed. > My concept of modules(including structure) is a source of generic > reusable classes by other specific classes that will be placed somewhere > and thus imported at some point. You can have multiple module paths. Modules still have to be named distinctly, but you can separate generic modules from those that implement specific use cases. > I'm curious about the performance part but mainly on how puppet and/or > ruby is loading those classes, as it seems to me like is ignoring my > classes inside the directory once a module with the same name is loaded. Apparently, you messed puppet up internally? Possibly a bug. If you must keep using non-modularized manifests (I hope you don't), rename your foo/ directory and change the import statement. That should fix it, right? Regards, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
