SteamOS Main rootfs size after steamos-unminimize --dev no longer allows enough space to rebuild key system packages

[matte-schwartz]

Your system information

• Steam client version: N/A
• SteamOS version: 20241126.1000
• Opted into Steam client beta?: Yes
• Opted into SteamOS beta?: Yes
• Have you checked for updates in Settings > System?: Yes

Please describe your issue in as much detail as possible:

Following the only workflow that I'm aware of for end-user on-device development (steamos-devmode enable -> steamos-unminimize --dev -> makepkg -si) now results in a standard out-of-space error for the rootfs when trying to build gamescope with Valve's PKGBUILD:

error: problem occurred while installing glm
error: could not open file /usr/lib/holo/pacmandb/local/glm-1.0.1-1/desc: No space left on device
error: could not update database entry glm-1.0.1-1
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.

This only started happening after KDE 6.2.2 was pushed to SteamOS Main, and I noticed that steamos-unminimize --dev now pulls in additional packages so I presume the base image size has increased.

I often need to rebuild gamescope as a part of testing and debugging for SteamOS, as I personally try to do my best with keeping issues organized and debugging them within that repository. Distrobox is not really an option considering how SteamOS usually runs behind upstream Arch repos so it's difficult to sync up package versions, and at least one of the gamescope PKGBUILD dependencies is only found in Valve's repos (powerbuttond).

Moving forward, what is going to be the best way for me to target SteamOS Main for development purposes?

Thanks!

[matte-schwartz]

was able to get around the space limitation for now by sudo pacman -Sing only the relevant packages for which I needed the include files, although I'm still dangerously low on rootfs space. until LLVM 19 gets pushed in Arch, I think an archlinux distrobox also works for the most part if using the standard gamescope build instructions (not the PKGBUILD)