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

add support for yum provider #20

Closed
wants to merge 7 commits into from

Conversation

jlambert121
Copy link
Contributor

Added support for the yum provider. I also had to mock the make dependency in the spec because it is no longer a valid git repo (but it exists on the forge).

Looking at the comments in the install, is < 1.0 support still needed?

jlambert121 and others added 2 commits November 13, 2013 15:49
After talking with @adrienthebo, distro packages of r10k should have git as a
runtime dependency. If they don't, they are broken and should be fixed
@jlambert121
Copy link
Contributor Author

@tampakrap i'm not following your comments. Are you proposing adding yum to the same case as pe_gem?

I didn't do that because RHEL based systems prefix gem packages with 'rubygem-'.

}
end
it { should include_class("git") }
it { should_not contain_package("rubyge-r10k")}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in the package name here

require git only when installing via gem or bundler
@acidprime
Copy link
Collaborator

@jlambert121 Thanks for the pull request, I agree that the yum does not necessarily need to be in the same case statement as pe_gem and gem for the time being. If you can rebase the updates in .fixtures.yml and fix your spec typo I will merge ( need to think about the recent conditional git change as well https://github.com/acidprime/r10k/pull/22 )

@jlambert121
Copy link
Contributor Author

Spec updated for #22, #23.

@tampakrap
Copy link
Contributor

I just filed PR #24 as alternative for this one

@jlambert121
Copy link
Contributor Author

Skimming #24 it looks like a better solution utilizing the params class rather than extending the conditional.

@tampakrap
Copy link
Contributor

I thought about it as well but unfortunately it's not possible. We need to set $package_name based on the final value of $provider, not the default value of $provider

@acidprime
Copy link
Collaborator

Yeah I am going to close this in lieu of #24

@acidprime acidprime closed this Nov 28, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants