[bug#72152] [PATCH] gnu: highlight: Use correct location for default configuration files.

[bug#72152] [PATCH] gnu: highlight: Use correct location for default configuration files.

[chris]

* gnu/packages/pretty-print.scm (highlight): Use correct location for default configuration files. Resolves missing filetypes.conf warnings.
[arguments]: Output default configurations to etc.

Change-Id: Ic9404cfb3490e5a212d46dfc483ee5eacbb906aa
---
 gnu/packages/pretty-print.scm | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/gnu/packages/pretty-print.scm b/gnu/packages/pretty-print.scm
index 220761fc07..e754b31668 100644
--- a/gnu/packages/pretty-print.scm
+++ b/gnu/packages/pretty-print.scm
@@ -369,11 +369,9 @@ (define-public highlight
     (arguments
      (list
       #:tests? #f ;no tests
-      #:make-flags #~(let ((confdir (string-append #$output
-                                                   "/share/highlight/config/")))
-                       (list (string-append "PREFIX=" #$output)
-                             (string-append "HL_CONFIG_DIR=" confdir)
-                             (string-append "conf_dir=" confdir)))
+      #:make-flags #~(list (string-append "PREFIX=" #$output)
+                           (string-append "HL_CONFIG_DIR=" #$output "/etc/")
+                           (string-append "conf_dir=" #$output "/etc/"))
       #:phases #~(modify-phases %standard-phases
                    (delete 'configure) ;no configure script
                    (add-after 'unpack 'fix-search-for-lua

base-commit: a800c49fb767f549fbc0eefe8dce6daa5da8604c
-- 
2.45.2

[bug#72152] explanation of patch

[chris]

This patch resolves a situation that causes an annoying warning, "cannot open filetypes.conf". The warning discussed in more detail here https://issues.guix.gnu.org/68948

To see the warning from the unpatched version, this shell command,
```
$ echo "(highlight (package bug))" | highlight -O xterm256 --syntax lisp
cannot open filetypes.conf: No such file or directory
(highlight (package bug))
```

Using the patched package definition, no warning is seen