Hmm...that's interesting.
As far as I know, there are no adverse side effects to just including
the other class in the dependent class.
I.e.
class pam-ldap {
include "openldap-client"
}
If anyone does know of a problem with this, could you shed some light on it?
It may increase compile time due to multiple includes, but I'm not
sure about that since, in theory, it should just be a noop if it's
already been included (haven't checked the code).
Trevor
On Wed, Mar 18, 2009 at 05:29, paul matthews
<paulsmatth...@googlemail.com> wrote:
> Have you tried within the Package instruction for pam-ldap:-
>
> require => Package["openldap-client"]
>
> or if the openldap-client package is wrapped up in a class
>
> require => Class["openldap-client"]
>
> Cheers
> Paul
>
> 2009/3/18 Ivo van der Meer <i...@crewtty.ath.cx>
>>
>> Hi,
>>
>> I have a class and want to depend on a Package from another class, how do
>> I
>> solve this ??
>> I have 2 classes one is called openldap-client and the other is called
>> pam-ldap. I want pam-ldap to depend on the openldap-client class which has
>> a Package called openldap-client.
>>
>> I've tried the following:
>>
>> - openldap-client::Package["openldap-client"]
>> - Class[openldap-client]::Package["openldap-client"]
>>
>> Has anyone got a good solution to this or is it a bad idea to make such a
>> dependency?
>>
>>
>> Kind regards,
>>
>> Ivo
>>
>>
>
>
>
> --
> Paul Matthews
> ----------------------------------------------------------------------
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
