You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 26, 2024. It is now read-only.
Many gem commands accept multiple gems from the command line, like gem fetch and gem check. The Gem::Command super class exposes a method called get_all_gem_names to list them. Our implementation for gem sign uses get_one_gem_name, which aborts unless there is exactly one gem name argument.
Maintainers that publish a family of gems together (like Rails and rspec) would probably appreciate something like:
gem sign rspec-core.gem rspec-rails.gem rspec-mocks.gem, or even gem sign *.gem. Our GemSigner class could accepts 1+ gems as input. It would challenge the caller once for authentication, acquire one certificate around a key pair, then sign all gems with the key.
Many
gemcommands accept multiple gems from the command line, likegem fetchandgem check. The Gem::Command super class exposes a method calledget_all_gem_namesto list them. Our implementation forgem signusesget_one_gem_name, which aborts unless there is exactly one gem name argument.Maintainers that publish a family of gems together (like Rails and rspec) would probably appreciate something like:
gem sign rspec-core.gem rspec-rails.gem rspec-mocks.gem, or evengem sign *.gem. Our GemSigner class could accepts 1+ gems as input. It would challenge the caller once for authentication, acquire one certificate around a key pair, then sign all gems with the key.