--- Begin Message ---
Subject: |
[PATCH] gnu: ruby-ruby-memcheck. |
Date: |
Mon, 15 Apr 2024 09:26:58 +0100 |
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 @@ (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
--- End Message ---
--- Begin Message ---
Subject: |
Re: [bug#70394] [PATCH] gnu: ruby-ruby-memcheck. |
Date: |
Sun, 19 May 2024 13:16:59 +0100 |
User-agent: |
mu4e 1.12.2; emacs 29.3 |
Christopher Baines <mail@cbaines.net> writes:
> 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
I've pushed this to master now as
a47cab5d286f81278af6e26a359f6429fd085e10.
signature.asc
Description: PGP signature
--- End Message ---