You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've already got this work started, but I had a question so I thought I'd start with where I am. I want to converge what we have grown in-house with this cookbook, and first thing blocking me is redhat support.
I see you have .debs in /debs, and I took a similar approach, creating an /rpms folder -- I'm not finding anything in the chef doc on how it would pick up those files. Are you just source controlling them for your convenience? How are you getting chef to use those files as the packages it installs with the package provider?
The text was updated successfully, but these errors were encountered:
Using packages in this manner is typically fine for development, especially if you have a poor connection; but for general use, packages available via the system's package manager should be preferred. You can install rpms with the rpm_package resource. Typically you would do something like:
where the rpm is located at my_cookbook/files/default/my_package.rpm.
I'll be building a centos compatible version of this that you may be interested in, but this cookbook doesn't seem to be being maintained, and there are issues with the licensing, so I'll be building a separate cookbook.
I've already got this work started, but I had a question so I thought I'd start with where I am. I want to converge what we have grown in-house with this cookbook, and first thing blocking me is redhat support.
I see you have .debs in /debs, and I took a similar approach, creating an /rpms folder -- I'm not finding anything in the chef doc on how it would pick up those files. Are you just source controlling them for your convenience? How are you getting chef to use those files as the packages it installs with the package provider?
The text was updated successfully, but these errors were encountered: