Open Shockwave508 opened 5 months ago
Currently the client doesn't have a concept of versions, in that it does not see the older content in there.
I could do some other things like either provide a mode to delete the cache files as soon as they are downloaded and used, which would save on disk but add more network traffic. Or have some logic to remove inside the folders files that don't match.
What are your thoughts @Shockwave508 ?
Currently the client doesn't have a concept of versions, in that it does not see the older content in there.
I could do some other things like either provide a mode to delete the cache files as soon as they are downloaded and used, which would save on disk but add more network traffic. Or have some logic to remove inside the folders files that don't match.
What are your thoughts @Shockwave508 ?
I think the latter is a good stopgap measure.
Latter is good. Will prevent obsolete copies piling up.
Feature Request
Multiple versions of a sourceport could easily stack whenever a new update is installed, within the .cache folder, gradually draining onboard disk space over time.
Solution
If a new version of a sourceport is downloaded through Luxtorpeda, delete the older, obsolete version after successful install.
Additional Context
No response