(name . Nicolas Goaziou)(address . firstname.lastname@example.org)(address . email@example.com)
Hi Nicolas, I was trying to ensure that when emacs-deadgrep is installed, ripgrep is also installed. The former doesn’t need the latter to build but does require it at runtime. Isn’t propagated-inputs the right field for that? Sent from my iPhone
Toggle quote (21 lines)> On Jul 7, 2021, at 7:20 AM, Nicolas Goaziou <firstname.lastname@example.org> wrote:> > Hello,> > Matthew James Kraai <email@example.com> writes:> >> * gnu/packages/emacs-xyz.scm (emacs-deadgrep)[propagated-inputs]: Add>> ripgrep.>> --->> gnu/packages/emacs-xyz.scm | 3 ++->> 1 file changed, 2 insertions(+), 1 deletion(-)>> >> Add ripgrep as propagated-input, as is done for emacs-ripgrep and>> emacs-rg.> > I think ripgrep should be an input. Both emacs-ripgrep and emacs-rg> needs to be fixed, too.> > Regards,> -- > Nicolas Goaziou
(name . Matthew Kraai)(address . firstname.lastname@example.org)(address . email@example.com)
Matthew Kraai <firstname.lastname@example.org> writes:
Toggle quote (5 lines)> I was trying to ensure that when emacs-deadgrep is installed, ripgrep> is also installed. The former doesn’t need the latter to build but> does require it at runtime. Isn’t propagated-inputs the right field> for that?
Inputs are also available at runtime, but do not clobber user's profile.It's preferable to use them, when it's reasonably possible. In this case, it means you just need to modify the Elisp source to makesure code points to the right ripgrep executable in the store. See,e.g., emacs-flycheck-grammalecte.