Skip to content
This repository has been archived by the owner on Mar 31, 2024. It is now read-only.

Define a cache directory inside the container #38

Open
livingsilver94 opened this issue Oct 4, 2022 · 2 comments
Open

Define a cache directory inside the container #38

livingsilver94 opened this issue Oct 4, 2022 · 2 comments
Labels
type: feature A new functionality to implement.

Comments

@livingsilver94
Copy link
Contributor

Some build systems (e.g. the Go bootstrapping, or gradle) use a cache directory. There's currently no environment variable set to provide one. We may set HOME or XDG_CACHE_HOME to solve the issue. Or both.

@ermo
Copy link
Member

ermo commented Oct 17, 2022

@livingsilver94

Which of the two is more prevalent? And which of the two is more correct?

I'm asking from the position of wondering whether projects which use $HOME instead of $XDG_CACHE_HOME would consider changing from $HOME to $XDG_CACHE_HOME if a bug was filed?

The pragmatic solution is to set both of course. Of the two, $XDG_CACHE_HOME seems the more correct solution to me.

@livingsilver94
Copy link
Contributor Author

livingsilver94 commented Oct 17, 2022

$XDG_CACHE_HOME is indeed more correct, and specific. Creating a custom cache directory inside $HOME is a behavior some non-xdg-conformant applications have.

Anyway, regardless of the caching necessity, the $HOME variable is assumed to be set by most Linux application for... uncountable reasons.

@livingsilver94 livingsilver94 added the type: feature A new functionality to implement. label Jul 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature A new functionality to implement.
Projects
None yet
Development

No branches or pull requests

2 participants