Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Added a `bundle licenses` cli task #1898
This commit adds a
After having felt the pain of walking through a Ruby application's dependencies to determine license information on several occasions, it would be a dream to me if more gem authors used the
I've added a new test for this change, and would love any and all feedback to this approach.
This seems like a perfect example of something that I would like to make possible via a Bundler plugin. We don't have a plugin system yet, but we want to make one so that things like this are easy to do without having to go into bundler core, which we want to keep smaller and more focused.
Since we don't have a plugin system worked out yet, it might be useful to accept this and then refactor it into a plugin when possible. @hone, what do you think?
On May 4, 2012, at 3:15 PM, Bryan Woodsreply@reply.github.com wrote:
Thanks for the feedback. I'd definitely love to see this added in order to begin encouraging developers to use the
I'm excited by the prospect of a bundler plugin system and would love to offer my time and help to make it happen. Would love to hear from the project maintainers about how they envision this working, any thought that's gone into it already, and how I might be able to help.
I would also like to see this change incorporated into Bundler (whether through a plugin or not). Being able to check that I didn't accidentally pull in a dependency with an incompatible license would be very useful.
It seems like it should be fairly core functionality to me. I should be able to ask my distribution system about the metadata of the software I've installed through it. (e.g. apt-cache showpkg, brew info).
For those who turn up here before this is implemented, I managed to hack around it with this:
(As an annoying note, only about 6 of the gems that I'm using provide this information in the Gemspec)