(address . guix-patches@gnu.org)
0161cd7e715da4b3758471c77a63f67b5736665e.1713169618.git.mail@cbaines.net
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(-)
Toggle diff (17 lines)
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 @@ (define-public ruby-ruby-memcheck
(("%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
base-commit: 58a0c85ad35db14c9fed7d5791b43d30882e13bf
--
2.41.0