-
Notifications
You must be signed in to change notification settings - Fork 178
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
feat(config): XDG_CONFIG_HOME
and XDG_CACHE_HOME
compliance
#1050
Conversation
Signed-off-by: Chawye Hsu <su+git@chawyehsu.com>
Signed-off-by: Chawye Hsu <su+git@chawyehsu.com>
Can we have similar behavior for |
good idea! |
Signed-off-by: Chawye Hsu <su+git@chawyehsu.com>
Signed-off-by: Chawye Hsu <su+git@chawyehsu.com>
XDG_CONFIG_HOME
complianceXDG_CONFIG_HOME
and XDG_CACHE_HOME
compliance
Signed-off-by: Chawye Hsu <su+git@chawyehsu.com>
Related to XDG compliance, I'm assuming that the installer will also respect these defaults? |
I'm asking because the documentation for the installation is not really explicit about this: https://pixi.sh/latest/ |
Could you also update the docs in : https://pixi.sh/latest/advanced/explain_info_command/#cache-dir |
He @anjos which installer did you mean? The rattler cache (the underlying installer in pixi) will also use it with this PR. But if you mean the the actual pixi binary this isn't changed by this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again @chawyehsu
Thanks to both of you! @ruben-arts: what I meant was what is installed with the command line |
Just to verify, you mean that we install into |
I apologise for the confusion - In short, I'm asking if pixi will also respect |
It's easy to do so since we already support |
That is what I'm currently doing, thanks! |
Close #1049