inviqa/chef-php-extra — pull request #25 by joonas-fi (2013-03-30 12:37:03+00:00)
Title: phpredis recipe: configurable revision + misc fixes

Hi,

It is good practice to provide overridable revision attribute so I can fix my configuration to use a revision of the dependency that is guaranteed to work. Of course the revision should default to "master".

I am only including in my Chef run list the "chef-php-extra::predis" recipe in my project, and it does not work as-is: Commit 454800f fixes missing build dependencies. Any suggestions on this approach? I know it's far from perfect (php version number, "php5-dev" package name in other distros etc).

I noticed there's a "module_dev" recipe which:
- Would bring php5-dev (in Ubuntu), but not "make"
- But it also includes "chef-php-extra" (=> "default" recipe), which includes stuff I don't want:
* module_mcrypt
* module_soap
* module_xml
* module_gd

I believe that any recipe should be runnable on their own, and they should only include stuff to get the software in the recipe to a working condition, i.e. not install anything else that is not required.

Commit 11ea2b4 fixes hardcoded cookbook name. I like to name the cookbooks without "chef-" prefix, as they're in "chef-cookbooks" directory anyways. Any reason why it's mentioned in the template block? It works just fine without it.

I noticed there are numerous recipes in the chef-php-extra cookbook which harcode the cookbook name. Do you know if there's any way to refer to current cookbook's recipe without hardcoding the cookbook name? (i.e. something like "::recipe_name"). Or am I completely lost in my hope to name cookbooks the way I like? :)

Thanks!