output interesting cpanm flags (closes #495) #496
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch makes CPAN Testers reporting seamless to cpanm users with App::cpanminus::reporter installed. It will conform to the server API via the common client, handle any supported transport mechanism and even setup a profile for new users. Since all a user needs to start sending reports is install App::cpanminus::reporter 0.10 or later, the patch also provides a '--skip-report' option for cpanm to opt-out from sending any reports.
|
@miyagawa ummm... I messed up the patch, sorry. Let me close this one and open a new one :( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
This is a small patch to display the most important cpanm running flags to the output (either STDOUT or build.log), right after the main header. This should fix #495 and help people debug their installations, specially since there are so many different tools relying on potentially different runs of cpanm (e.g. carton).
If everything goes as expected, no one will even see it. But if you're skimming through your build.log output, it's probably because something didn't go as expected, so I think it'd be good to see at least how that run was made by cpanm.
Of course, if you merge this, please feel more than welcome to change the text formatting and what options get logged. I just put the ones I thought would be interesting :)
Thanks again for the incredible work!