Alt Text

A screenshot of a file manager preview window for my ~/.cache folder, which takes up 164.3 GiB and has 246,049 files and 15,126 folders. The folder was first created about 1.75 years ago with my system

      • brakenium@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        My update script handles mirrors, updates and cleans the cache automatically. I’d definitely recommend creating one. It’s aliased to sysupdate for me and I also check if it’s a debian or arch based distro so the command works on my servers and desktop

          • brakenium@lemm.ee
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            I’ve heard of tools like that, but this works fine for me. This way I’m not dependent on it being packaged for my distro and having to install it through other means. I’m fine running things manually, this is just for convenience

          • brakenium@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            I don’t think I’ve posted it before, but here it is. If you use different utilities you’d have to swap those out. Also excuse the comments, I had GH Copilot generate this script

    • EddyBot@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      it doesn’t matter if you use paru, yay or heck makepkg if you are compiling packages with hilariously large sources like for example webbrowser (librewolf, brave, ungoogled-chromium, firedragon take each like ~30 GB) without pruning the build cache afterwards

      • Zangoose@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Something I noticed was that in this case it was mostly binary AUR programs taking up the space.

        I think maybe since yay/AUR use cloned git repos, and old versions of binaries get stored in the git diff and then add up because different versions of the binary are basically like keeping multiple copies of it instead of just the changes to the source code.