From 3be53e4e8ab214a836c9c96265e69bc894190fa7 Mon Sep 17 00:00:00 2001
From: Trevor Bender <Trevor.Bender@gmail.com>
Date: Sat, 28 Dec 2024 19:46:32 -0500
Subject: [PATCH] fix: epm domain config file can be a symlink

With v0.21.0, if the custom package domain file is a symbolic link
epm commands will fail with:

```text
=> No config file for domain 'my.custom.domain'
```

This may be the case if the file is managed by something like stow,
nix, or home-manager.

Fix by following symbolic links.

issue: #1833
---
 pkg/mods/epm/epm.elv | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pkg/mods/epm/epm.elv b/pkg/mods/epm/epm.elv
index 10480d206..f07b7a2d5 100644
--- a/pkg/mods/epm/epm.elv
+++ b/pkg/mods/epm/epm.elv
@@ -185,7 +185,7 @@ fn -write-domain-config {|dom|
 fn -domain-config {|dom|
   var cfgfile = (-domain-config-file $dom)
   var cfg = $false
-  if (path:is-regular $cfgfile) {
+  if (path:is-regular &follow-symlink=$true $cfgfile) {
     # If the config file exists, read it...
     set cfg = (from-json < $cfgfile)
     -debug "Read domain config for "$dom": "(to-string $cfg)