Puppet users - Feb 2010 - naming inherited classes vs namespace children.

Do other people have a consistent naming system for distinguishing
between sub-classes that are simply namespace children versus those
that actually inherit from another class?

ie the following setup

class foo { }
class foo::bar { }

vs.

class foo { }
class foo::bar inherits foo { }


I''m considering doing something like:

class foo { }
class foo::ham { }
class foo::foo_eggs inherits foo { }


but I don''t really like it.

-- 
nigel

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Feb 13, 6:53 pm, Nigel Kersten <nig...@google.com>
wrote:
> Do other people have a consistent naming system for distinguishing
> between sub-classes that are simply namespace children versus those
> that actually inherit from another class?
I do not have such a system to offer, in part because I have never
conceived a need for one.  Your setup is much more complicated than
mine, I think, so you surely have needs that I do not, but are you
certain this is one of them?  In other words, what problem do you
solve by encoding that distinction into class names?


John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Mon, Feb 15, 2010 at 5:58 AM, jcbollinger <John.Bollinger@stjude.org>
wrote:
>
>
> On Feb 13, 6:53 pm, Nigel Kersten <nig...@google.com> wrote:
>> Do other people have a consistent naming system for distinguishing
>> between sub-classes that are simply namespace children versus those
>> that actually inherit from another class?
>
> I do not have such a system to offer, in part because I have never
> conceived a need for one.  Your setup is much more complicated than
> mine, I think, so you surely have needs that I do not, but are you
> certain this is one of them?  In other words, what problem do you
> solve by encoding that distinction into class names?
Not having to delve into a given class to work out how it behaves.

I have a lot of part-time Puppet manifest maintainers. They don''t do
it regularly, and I''ve tried to keep a short leash on a lot of the
more complicated Puppet features for this reason.

It''s by no means necessary. It''s just bothering me, so I
thought I''d
see whether anyone else has an elegant solution... :)
>
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
nigel

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.