Issue #2636 has been updated by Nigel Kersten.
Gah. A missing "not" messed that up completely, sorry. Currently the main method for foo::bar is to define it in `foo/manifests/bar.pp`, and I'd prefer us to not support that, *and* `foo/manifests/bar/init.pp` as I think it would get rapidly confusing for people, but maybe I'm wrong there. We'd have to deprecate the "not-init.pp" method if we only wanted to offer one way of doing this is what I meant. Is the benefit of doing this greater than the cost of having two methods? ---------------------------------------- Feature #2636: Improvement to module organization https://projects.puppetlabs.com/issues/2636 Author: R.I. Pienaar Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: modules Target version: 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.
