Git sources don't respect the --quiet option #1830
Comments
Confirm. |
We can probably fix this just by passing -q to git in quiet mode. On Nov 30, 2012, at 3:49 AM, Rohit Arondekar notifications@github.com wrote:
|
The updating part already passes |
I think we are attempting to provide more feedback during the install process -- can you add quiet only if Bundler's quiet mode is on? Thanks. :) On Nov 30, 2012, at 10:16 PM, Rohit Arondekar notifications@github.com wrote:
|
Hmm finding out whether the option quiet is set is not trivial unless I'm missing something. The creator of def git(uri, options = {}, source_options = {}, &blk)
unless block_given?
msg = "sniped"
raise DeprecatedError, msg
end
source Source::Git.new(_normalize_hash(options).merge("uri" => uri)), source_options, &blk
end Any ideas on how to proceed? One way might be to capture the output and output to screen via Bundler.ui so it obeys the quiet option. |
You might be able to get the quiet value from Bundler.ui.quiet? (or write that method). On Nov 30, 2012, at 11:11 PM, Rohit Arondekar notifications@github.com wrote:
|
Merged #2194 |
My Gemfile includes different gems via git.
When using bundler with the --quite option those gems still result in console output produced by git.
This is especially annoying when using bundler and capistrano.
Thanks :)
The text was updated successfully, but these errors were encountered: