I have a module, `last/dotplot`, whose tests on co...
# modules
c
I have a module,
last/dotplot
, whose tests on conda used to pass but now fail. The following patch fixes the problem of tests failing, but… I have the impression that the main conclusion is that the module is not going to work with conda in most users's hands. Can a conda user tell me a robust way to find a file installed by a conda package?
Copy code
diff --git a/modules/nf-core/last/dotplot/main.nf b/modules/nf-core/last/dotplot/main.nf
index 0d4e93643..f9aa8ab8d 100644
--- a/modules/nf-core/last/dotplot/main.nf
+++ b/modules/nf-core/last/dotplot/main.nf
@@ -29,7 +29,7 @@ process LAST_DOTPLOT {
     def annot_b_arg = annot_b ? "-b ${annot_b}" : ''
     def input_command = filter ? "maf-linked ${args2}" : "zcat -f"
     """
-    TTF=/home/ubuntu/conda_pkgs_dir/open-fonts-0.7.0-1/fonts/open-fonts/DejaVuSansMono-Regular.ttf
+    TTF=/home/runner/conda_pkgs_dir/open-fonts-0.7.0-1/fonts/open-fonts/DejaVuSansMono-Regular.ttf
     [ -e "\$TTF" ] || TTF="/opt/conda/fonts/open-fonts/DejaVuSansMono-Regular.ttf"
     $input_command $maf |
     last-dotplot \\
s
I guess just search globally for DejaVuSansMono-Regular.ttf?
c
I can run a
find
but then when the module runs the user's machine how can I avoid the possibility that it will traverse directories with millions of files? Are there environment variables or nextflow variables that are guaranteed to be available in all cases and tell where conda modules have been installed?