You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible for stack to compare the current stack.yaml's packages to the contents of .stack-work/downloaded and remove the unused folders? These tend to accumulate when working on a project with fast-moving GitHub-hosted dependencies. Thanks.
The text was updated successfully, but these errors were encountered:
Indeed, it'd be good to garbage collect those. One tricky thing here is that users may have multiple stack.yaml files that refer to different git repos. I suppose one approach could be to read all *.yaml in the dir, and GC based on those.
Could potentially have an explicit command to clean up such things - #133 - note that stack clean --full is one approach, but that's a rather big hammer since it throws away everything.
A further complication is that it's likely that downloaded git repos will be shared between different projects - #3551 . One approach that'd apply generally to garbage collection would be to have it maintain a list of locations of stack configuration files, possibly storing last usage time.
So, in summary, it would definitely be good to fix this, probably while addressing the other garbage collection issues.
Is it possible for stack to compare the current
stack.yaml
's packages to the contents of.stack-work/downloaded
and remove the unused folders? These tend to accumulate when working on a project with fast-moving GitHub-hosted dependencies. Thanks.The text was updated successfully, but these errors were encountered: