Re: [Puppet Users] Classes, Subclasses, and Requirements

2012-05-17 Thread James Sweeny
The point of the "require" parameter is to define a dependency relationship. In the example you gave, it doesn't really make sense to have the exec require a class that does nothing (test2::foo), so you can drop the require. On the other hand, if the exec actually needed test2::foo to work correct

Re: [Puppet Users] Classes, Subclasses, and Requirements

2012-05-17 Thread LTH
On Thursday, May 17, 2012 11:23:40 AM UTC-4, James Sweeny wrote: > > You can't require Class['test2::foo'] unless it's already available where > you're requiring it. You need to include test2::foo in test2::bar. > > Thanks. If I include test2:foo in test2::bar, do I still need require => [Class

Re: [Puppet Users] Classes, Subclasses, and Requirements

2012-05-17 Thread James Sweeny
You can't require Class['test2::foo'] unless it's already available where you're requiring it. You need to include test2::foo in test2::bar. On Thu, May 17, 2012 at 10:53 AM, LTH wrote: > Hello, > > I'm having some trouble with subclasses accessing other subclasses within > the same main class.