Hello! I'm doing some analysis of installed Ruby gems, specially those that require a compiler toolchain to be installed.
This analysis will help me determine an usage pattern and potentially work with gem authors to improve platform support for those gems.
Will be great if you can help me collect this information.
You can run the script below in your machine and copy over the output as comment to this Gist. Even better, if you can run this within your application directory, to ensure it collects all possible binary gems your application uses.
In case of doubt, you can inspect the annotated code of the script below. No
sudo
or other weird things are required except for curl
utility be
installed.
Thank you in advance for your help!
If you install gems using rvm's gemsets or install gems with a specific path
(ie. bundle install --path
or bundle install --deployment
), your application
gems will not be visible.
Please prepend bundle exec
to the ruby
command shown below.
The following are simple one-liner commands to invoke the script and copy the results directly to the clipboard.
$ curl -L https://bit.ly/list-binary-gems | ruby | xclip -sel c
Note: Please change ruby
to bundle exec ruby
if using bundler or
gemsets in your application.
$ curl -L https://bit.ly/list-binary-gems | ruby | pbcopy
Note: Please change ruby
to bundle exec ruby
if using bundler or
gemsets in your application.
Of those gems, I am the author or co-author of the following ones:
I'm happy to assist with improving tooling support for those gems, which are possibly a bit unique in this list because they are not C extensions - they use FFI, but they use a compiler toolchain to build the shared library that we link our FFI calls against. They should all have a similar enough build pattern that supporting one probably means supporting all of them.
If you want to reach out to me, you can feel free to file issue tickets on the GitHub repos for those gems.