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

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

      It looks like yay was storing AUR build files there, that folder took up about 160 of the 164GiB

      • SuperIce@lemmy.world
        link
        fedilink
        English
        arrow-up
        21
        ·
        1 year ago

        You can use yay -Sc to clean the cache. It’ll also ask you if you want to clean the pacman cache, which I’m assuming you also haven’t cleaned (check the size of /var/cache/pacman).

        • 30p87@feddit.de
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          One would just need to modify the pacman cache hook for yay. I’m too lazy tho.

      • MonkderZweite@feddit.ch
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        1 year ago

        Shouldn’t it store that stuff in data-home or state-home? Pikaur compiles in cache and stores it in data-home after.

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

          • 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

      • SuperIce@lemmy.world
        link
        fedilink
        English
        arrow-up
        13
        ·
        1 year ago

        Pacman’s cache isn’t in ~/.cache though, it’s in /var/cache. So whatever is taking up this much space isn’t the package manager.

        That being said, I think the arch devs should add a config option to automatically delete old packages without having to run paccache manually and have it default to the last 2 versions of a package or so. It can grow quite big over time.