Package: snapd Version: 2.30-5+b1 Severity: normal Tags: upstream snapd drops huge amounts of crap in /snap (a FHS violation, incidentally), /var/snap, /var/lib/snapd, and $HOME/snap *none* of which are configurable locations.
Their excuse is that you can just bind mount any/all of the three (because symlinking doesn't really work either). Imagine if all developers pulled that crap and you had to set up 3 bind mounts (or symlinks) for every piece of software... -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages snapd depends on: ii adduser 3.117 ii apparmor 2.12-4 ii ca-certificates 20180409 ii gnupg 2.2.8-1 ii libapparmor1 2.12-4 ii libc6 2.27-4 ii libcap2 1:2.25-1.2 ii libseccomp2 2.3.1-2.1 ii libudev1 239-7 ii openssh-client 1:7.7p1-4 ii squashfs-tools 1:4.3-6 ii systemd 238-4 snapd recommends no packages. snapd suggests no packages. -- no debconf information
