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

Specify dependent module in dependencies #68

Merged
merged 1 commit into from
Jul 31, 2019

Conversation

nabertrand
Copy link

This commit adds the origin of the dependency to verbose output, making it easier to determine which
source/module is causing a conflict.

For example:

Failed to resolve puppetlabs-concat (= 5.1.1) <https://forgeapi.puppetlabs.com>

becomes

Failed to resolve puppetlabs-concat (= 5.1.1) <https://forgeapi.puppetlabs.com> (from Puppetfile)

This commit adds the origin of the dependency to
verbose output, making it easier to determine which
source/module is causing a conflict.

For example:
Failed to resolve puppetlabs-concat (= 5.1.1) <https://forgeapi.puppetlabs.com>
becomes
Failed to resolve puppetlabs-concat (= 5.1.1) <https://forgeapi.puppetlabs.com> (from Puppetfile)
@ekohl
Copy link
Member

ekohl commented Nov 2, 2018

This is a really annoying problem you're solving so a big thanks. I'm not really familiar with the code base. Would it be possible to have tests for this?

@nabertrand
Copy link
Author

I'm sure I could come up with some tests. I ended up having to bring over entire methods from librarianp in order to alter dependency initialization, but now I'm wondering if it doesn't make more sense to add this feature to librarianp in order to limit the required changes to this gem. Thoughts?

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

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

I don't know librarian but I can confirm this provides much more useful feedback. I wouldn't mind merging this.

@bastelfreak bastelfreak merged commit abeace5 into voxpupuli:master Jul 31, 2019
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