summaryrefslogtreecommitdiff
path: root/man/bundle-lock.1
diff options
context:
space:
mode:
authorBundlerbot <bot@bundler.io>2019-10-30 11:30:02 +0000
committerBundlerbot <bot@bundler.io>2019-10-30 11:30:02 +0000
commite70643c1be3a4417bd537d7e63470265465e693e (patch)
treec33c8f292c9899547b8e4877d97043995e452fb7 /man/bundle-lock.1
parent5bc9c5868307679b79cdb7e4026da5f9e3888c63 (diff)
parentca2af534a6464018aa1a62428369bef349b5218e (diff)
downloadbundler-e70643c1be3a4417bd537d7e63470265465e693e.tar.gz
Merge #7376
7376: bundle info prints gem metadata r=deivid-rodriguez a=orien ### What was the end-user problem that led to this PR? Rubygems has supported [gemspec metadata](https://guides.rubygems.org/specification-reference/#metadata) since version 2.0. I think it'd be great to display this information in response to the `bundle info <gem>` command. ### What is your fix for the problem, implemented in this PR? Added a check for `metadata`, outputting this extra information if it has been included with the gem release. For example: ``` > bundle info rspec-mocks * rspec-mocks (3.8.1) Summary: rspec-mocks-3.8.1 Homepage: https://github.com/rspec/rspec-mocks Documentation: https://rspec.info/documentation/ Source Code: https://github.com/rspec/rspec-mocks Changelog: https://github.com/rspec/rspec-mocks/blob/v3.8.1/Changelog.md Bug Tracker: https://github.com/rspec/rspec-mocks/issues Mailing List: https://groups.google.com/forum/#!forum/rspec Path: /opt/asdf/installs/ruby/2.6.5/lib/ruby/gems/2.6.0/gems/rspec-mocks-3.8.1 ``` For better readability, we could align the values. However, this would mean a change to the existing info property lines (`Summary`, `Homepage`, `Path` and `Default`). Which would potentially break existing scripts that are coupled to the precise output. Co-authored-by: Orien Madgwick <_@orien.io>
Diffstat (limited to 'man/bundle-lock.1')
0 files changed, 0 insertions, 0 deletions