From 945b334d443fa2290424f8081447dff59b407fac Mon Sep 17 00:00:00 2001 From: Christopher Baines Date: Mon, 15 Apr 2024 09:26:58 +0100 Subject: gnu: ruby-ruby-memcheck. 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 --- gnu/packages/ruby.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gnu/packages/ruby.scm b/gnu/packages/ruby.scm index 0541bb9562..5e34109a59 100644 --- a/gnu/packages/ruby.scm +++ b/gnu/packages/ruby.scm @@ -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 -- cgit v1.2.3