Issue #2636 has been updated by Nigel Kersten.
So this has always bugged me a little, but I'm unsure whether we want to continue heading down the path of providing more than one way to lay out modules. Ignoring the fact we can declare classes in all sorts of ways in random files, nested, using imports, etc is this really worth that? ---------------------------------------- Feature #2636: Improvement to module organization https://projects.puppetlabs.com/issues/2636 Author: R.I. Pienaar Status: Needs design decision Priority: Normal Assignee: Nigel Kersten Category: modules Target version: Statler Affected Puppet version: 0.25.0 Keywords: Branch: hello, In the case where someone wants to create classes like this: apache apache::php apache::php::gd apache::php::mysql etc it would be nice if all php related classes was in one sub directory, currently that isn't possible without the help of import, it would be great if the above classes could be laid out like this in addition to the current behaviour: apache/manifests/php/init.pp <- apache::php apache/manifests/php/gd.pp <- apache::php::gd at present we would need to have apache/manifests/php.pp apache::php class in a different directory than the rest of the php stuff. -- 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.
