Issue #4132 has been updated by Jeff McCune.
As a recommendation, the module payload could be moved one level deeper into the package contents. Instead of pupeptlabs-gcc-0.0.2/manifests/init.pp, the new layout could be puppetlabs-gcc-0.0.2/gcc/manifests/init.pp. This layout will also facilitate a single module "download" being used in multiple module paths by simply symbolic linking the "gcc" path component into the module path. -Jeff ---------------------------------------- Bug #4132: Module package contents should match the class name http://projects.puppetlabs.com/issues/4132 Author: Jeff McCune Status: Unreviewed Priority: High Assigned to: Category: Target version: Keywords: class directory package module autoloader Branch: Affected URL: Summary: When extracting a module from the forge, e.g. puppetlabs-gcc, the resulting directory name does not match the class name in init.pp, which will prevent the autoloader from finding the class. Expected Behavior: If a module provides a class "gcc" the module directory name should be "gcc" to facilitate autoloading. Actual Behavior: The class in init.pp does not match the directory in the package tarball. # puppetlabs-gcc-0.0.2/manifests/init.pp class gcc { include gcc::params package { $gcc::params::gcc_package: ensure => installed } } Here, puppetlabs-gcc-0.0.2 should be simply "gcc" to match the class name inside of init.pp. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
