-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cabal-install-parsers: support XDG #655
Comments
TBH, this situations just sucks, so I'd suggest to define
That remark is specifically makes me don't want to do anything with this issue,. In fact, I'm even considering making |
This response makes no sense.
So either fix it or stop providing this API so that you don't break other downstream tools like ghcup, which assume that dependencies are reasonably maintained. |
Am I forcing you to use it? |
Are you deliberately providing broken API? |
No. Just outdated, there is a known limitation. The OP wrote
are there still plans to change it? The 3.10 and 3.12 documentation seems to be the same. @hasufell your tone is not motivating me to look into this issue any time soon. |
No one asked you to work on this. People can provide PRs. Your response suggests:
In that case that's a good reason to avoid any of your packages in the future. |
@phadej If you proceed with it, how will you warn Haskell-CI users? |
About what? |
Ok, so that would entirely be confined to direct users of |
(From haskell-hvr/cabal-plan#92)
cabal-install
3.10 uses XDG paths. For example in my system the config file is~/.config/cabal/config
and the store is~/.local/state/cabal/store
.Cabal.Config:readConfig
does not return the correct paths.To know whether to enable XDG support,
cabal-install
first looks at$CABAL_DIR
. If that variable is set, everything will be in there, as before. Otherwise, it checks whether$XDG_CONFIG_HOME/cabal
and~/.cabal
exist, and enables or disables XDG support. If both are present,~/.cabal
takes priority, but that's considered a mistake and likely to change: haskell/cabal#8577You can find a list of paths here and here. See also the relevant functions from the directory package.
In the future, something like this could be used: haskell/cabal#8879
The text was updated successfully, but these errors were encountered: