- From: Andrea Campi <
>
- To: "
" <
>
- Cc: "
" <
>
- Subject: [chef] Re: How to deal with cookbook dependence for other Distro/OS's
- Date: Fri, 21 Oct 2011 09:03:34 +0200
A trick I've used when in a rush:
If the dependency is only In the manifest, and you're positive you don't need
eg jpackage on any of your nodes, you can just stub it out.
That is, create a new empty jpackage cookbook and upload that one.
Not a long-term solution, but it may help in the short term. YMMV
On Oct 20, 2011, at 10:32 PM, Zuhaib Siddique
<
>
wrote:
>
Hey,
>
>
So it seems some of the cookbooks from Opscode by default set depends
>
statements in their metadata.rb for cookbooks that are required by a
>
particular OS/Distro. In the case of say tomcat cookbook it sets jpackage
>
as a dependence but you only need that for RPM base Distro's. Since I am
>
deploying on a Ubuntu box I am not included jpackage in the run list and
>
that made it very unhappy. So I just removed it from the metadata.rb but I
>
am just wondering if this is what is expected to be done by the cookbook
>
provided by opscode?
>
>
Thanks
>
Zuhaib
Archive powered by MHonArc 2.6.16.