[rubygems/rubygems] Don't warn on bundler binstubs --standalone --all
Prior to this commit bundle binstubs --standalone --all would output a warning about not being able to generate a standalone binstub for bundler.
This warning predates the --all option, and I don't think it makes sense in this context. The warning makes good sense when explicitly trying to generate a bundler standalone binstub with bundle binstubs bundler --standalone, since that command won't do what the user might have expected. But --all is not specifically asking for bundler, and having it report each time that the bundler binstubs could not be generated does not seem particularly helpful. The only way to make that warning go away would be to stop using --standalone --all.
This commit skips the warning when running with the --all option.
Added by dodecadaniel (Daniel Colson) almost 3 years ago
[rubygems/rubygems] Don't warn on bundler binstubs --standalone --all
Prior to this commit
bundle binstubs --standalone --allwould output awarning about not being able to generate a standalone binstub for
bundler.
This warning predates the
--alloption, and I don't think it makessense in this context. The warning makes good sense when explicitly
trying to generate a bundler standalone binstub with
bundle binstubs bundler --standalone, since that command won't do what the user mighthave expected. But
--allis not specifically asking for bundler, andhaving it report each time that the bundler binstubs could not be
generated does not seem particularly helpful. The only way to make that
warning go away would be to stop using
--standalone --all.This commit skips the warning when running with the
--alloption.https://github.com/rubygems/rubygems/commit/e6a72e19eb