boulder-d-legacy icon indicating copy to clipboard operation
boulder-d-legacy copied to clipboard

Define a cache directory inside the container

Open livingsilver94 opened this issue 3 years ago • 2 comments

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.

livingsilver94 avatar Oct 04 '22 08:10 livingsilver94

@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.

ermo avatar Oct 17 '22 06:10 ermo

$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 avatar Oct 17 '22 07:10 livingsilver94