Open christopher-hopper opened 9 years ago
I'm using both the php-pecl-memcache
and php-pecl-memcached
modules on RHEL, and have never needed an exception. What's wrong with just the following?
php::module { 'pecl-memcache': }
I guess that the problem is that we want this defined type to not require OS or Distro specific patterns in order to use. My puppet manifests will be used on Debian and RHEL builds, so I'd like to be able to use:
php::module { 'memcache': }
In the same way I can use:
php::module { 'apc': }
and have it just work on Debian or RHEL. Does that make sense?
When installing the memcache php module on RHEL, use the package 'php-pecl-memcache' in a similar way to the existing apc php module.
NOTE if more of these exceptions to package names are encountered, it might be worth defining all module package names in a hash or array, to simplify the branching and
php::param
variables.