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

don't explicitly include puppet-lint #183

Merged
merged 1 commit into from
Jun 24, 2016

Conversation

bastelfreak
Copy link
Member

we've multiple gems as puppet-lint plugins that all requier puppet-lint

we've multiple gems as puppet-lint plugins that all requier puppet-lint
@bastelfreak
Copy link
Member Author

We should discuss if we want to pull it from rubygems instead of git directly or if we want it as an implicit dep. based on a discussion at voxpupuli/puppet-corosync#292

@alexjfisher
Copy link
Member

LGTM. Personally, I'd say go with the released version.

@rnelson0
Copy link
Member

PLEASE do not pull from head, or sometime in the future modules will pull 3.0.0 directly but the checks will be looking for '>= 1.0.0', '< 3.0.0' and the world will be broken again. 100% on board with this change as is to prevent that from happening. Again.

@jyaworski jyaworski merged commit 2f49ca4 into voxpupuli:master Jun 24, 2016
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.

4 participants