Issue #2053 has been updated by luke.
Status changed from Unreviewed to Needs design decision
I can't decide on this one. There's an easy workaround:
<pre>
class foo::xen {
include ::xen
}
</pre>
But I suppose there should at least be a warning.
Am I misreading expected behaviour that much? It seems reasonable that any
mention of 'xen' inside of a xen class would normally refer to itself. Keep in
mind that we've got a general class lookup mechanism - 'include' doesn't have
its own class lookup.
----------------------------------------
Bug #2053: including a class with the same name subclass yields an unexpected
result
http://projects.reductivelabs.com/issues/2053
Author: lludwig
Status: Needs design decision
Priority: Normal
Assigned to:
Category:
Target version:
Complexity: Unknown
Affected version: 0.24.7
Keywords:
If you create a subclass with the same as a class you include, you get an
unexpected result.
Test code is listed here.
http://pastie.org/409446
It appears that any include inside of subclass thinks it references itself
first.
----------------------------------------
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://reductivelabs.com/redmine/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
-~----------~----~----~----~------~----~------~--~---
