Overlapping major versions error

[pbrisbin]

In our projects, we use stack-all to maintain our set of LTS configurations:

% ls -1 stack-lts*
stack-lts18.yaml
stack-lts19.yaml
stack-lts20.yaml
stack-lts21.yaml
stack-lts23.yaml
stack-lts24.yaml

And then, so that a bare stack still "just works", we symlink stack.yaml to whatever is latest:

% ls -l stack.yaml
lrwxrwxrwx 1 patrick patrick  16 Apr 21 10:05 stack.yaml -> stack-lts24.yaml

This works really well for us, we only maintain the concrete -ltsX files, but tooling that expects a stack.yaml also continues to work without issue. But when I upgrade stack-all , I now get an error:

% stack-all build --dry-run
...

stack-all-0.7.1: overlapping major versions: stack.yaml stack-lts24.yaml

What are your thoughts on accounting for this scenario?

I'd rather not use --keep-going to keep going on any error, but I'd like to skip passed this one. Or maybe stack-all should ignore symlinks?

I'm happy to PR a solution, but I'm not sure which direction you'd prefer (if any).

[pbrisbin]

FWIW, I just made the following change locally, and it works well:

readStackConfigs :: IO [ConfigVersion]
readStackConfigs =
  listDirectory "." >>=
  traverse dereferenceSymlink >>=
  fmap sort . mapMaybeM readStackYaml . mapMaybe readConfigFile . nub

dereferenceSymlink :: FilePath -> IO FilePath
dereferenceSymlink t = do
  isLink <- pathIsSymbolicLink t
  if isLink then getSymbolicLinkTarget t else pure t

I think this a pretty simple fix that is not disruptive or unexpected to anyone not using symlinks, or using them differently.