gnu: ruby-ruby-memcheck: Use non-interactive valgrind.
Use valgrind rather than valgrind/interactive, as this doesn't have gdb as an input, which makes it easier to update gdb. * gnu/packages/ruby.scm (ruby-ruby-memcheck)[inputs]: Use valgrind. Change-Id: Icfcee2c27fc41e68e1a34b38c043ece188cc56af
This commit is contained in:
		
							parent
							
								
									e9b25a6c6c
								
							
						
					
					
						commit
						a47cab5d28
					
				
					 1 changed files with 1 additions and 1 deletions
				
			
		| 
						 | 
				
			
			@ -10114,7 +10114,7 @@ Profiling multiple threads simultaneously is supported.
 | 
			
		|||
                (("%x\\(git ls-files -z)")
 | 
			
		||||
                 "`git ls-files -z`")))))))
 | 
			
		||||
    (native-inputs (list ruby-rake-compiler ruby-rspec))
 | 
			
		||||
    (inputs (list valgrind/interactive))
 | 
			
		||||
    (inputs (list valgrind))
 | 
			
		||||
    (propagated-inputs (list ruby-nokogiri))
 | 
			
		||||
    (synopsis "Valgrind memcheck tool for Ruby")
 | 
			
		||||
    (description "The @code{ruby_memcheck} gem provides a sane way to use
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Reference in a new issue