Issue #1612 has been updated by Joshua Corbin.
My scenario that caused me to hit this:
* General module widget defines general characteristics of widget
* Specific module suite pulls together multiple widgets, and adds
project-specific settings
e.g.
<pre>
class widget {
package {widget: ...}
service {widgetd: ...}
file {widget.conf: ...}
}
class suite::widget inherits widget {
File[widget.conf] {
source => "puppet:///modules/suite/widget.conf";
}
}
class suite {
include suite::widget
}
</pre>
Really, this comes down to an issue of what kind of organization layout makes
sense. Right now, it feels like Puppet is being artificially restrictive for
unclear reasons.
----------------------------------------
Feature #1612: Parent classes should not need dissimilar names
http://projects.puppetlabs.com/issues/1612
Author: Digant Kasundra
Status: Needs design decision
Priority: Normal
Assigned to:
Category:
Target version:
Affected version: 0.24.4
Keywords:
Branch:
<pre>
class cat {
exec { "/bin/echo I'm a cat": }
}
class tom::cat inherits cat {
exec { "/bin/echo I'm a tomcat": }
}
include tom::cat
</pre>
Parent classes must have dissimilar names at line 7 on node henson1
--
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.
