decide on the final feature set of this application

[magiruuvelvet]

Right now, this application only performs read-only operations and acts as a centralized "reporting" tool for caches and package managers. It also validates if the configured symbolic links are still present and point to the correct location. I have not decided yet if this application should also manage writing (like managing symbolic links, deleting caches, etc.), as such operations need to be designed very carefully, especially when operating directly on the user's home directory. Nobody likes applications which randomly delete important files due to a bug.

Pros for write operations

• convenient setup of symbolic links
• convenient configuration of cache locations for package managers with a configuration file (eg: npm and composer can read the cache location from a file)
• easily clear caches using filters (eg: files older than, delete all caches from a specific package manager)
• automatic and periodic clean-ups of ancient unused caches

Cons against write operations

• more implementation required, which increases code complexity
• bugs could delete the wrong files

If I decide to keep this application read-only, it should probably be renamed to a more fitting name, as it technically wouldn't "manage" anything, only observe and report.

[magiruuvelvet]

I've decided NOT to implement deletion features for v1.0. Version 1 should become a useful cache reporting and tracking tool to keep track of storage wasters.