Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added support for CentOS 6.x package names #1

Closed
wants to merge 1 commit into from

Conversation

jmccaffrey42
Copy link

In CentOS and RHEL 6.x, php53* packages have been renamed to php* to reflect the fact that versions of php prior to 5.3 are not supported and 5.3 is the official version of Cent and RH 6.

I have changed the package references to include this update so that the php cookbook works on CentOS and RHEL 6.x

@mikebranski
Copy link

Cheers for this. Ran into this issue last night.

@jmccaffrey42
Copy link
Author

No problem, it would be nice if someone from Chef would pull it though ;)

On May 11, 2012, at 7:29 AM, Mike Branskireply@reply.github.com wrote:

Cheers for this. Ran into this issue last night.


Reply to this email directly or view it on GitHub:
#1 (comment)

@dkingofpa
Copy link

@jmccaffrey42 I'd bet Opscode wants to include your changes. However, you'll need to follow the contribution process. That's in place so they can manage all the pull requests and satisfy the Apache licensing for the code you contribute.

@jtimberman
Copy link

Hello,

I apologize for the lack of response on this pull request, however we don't generally review individual pull requests that don't have a corresponding ticket in our ticketing system and set to the "Fix Provided" state. This is over a year old now, and that workflow is a bit newer, though.

Anyway, I don't believe that this particular issue is relevant in the current code base and released version of this cookbook. Thank you!

Joshua

@jtimberman jtimberman closed this Jun 15, 2013
Rockstar04 pushed a commit that referenced this pull request Jul 6, 2015
Small changes to FreeBSD support
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants