3 ms·

Snap needs to fix their non-standard directory placement. They ignore the FHS [1] by creating /snap at the root level. And they ignore XDG [2] by persistently c

by cpburns2009 8y ago

Snap needs to fix their non-standard directory placement. They ignore the FHS [1] by creating /snap at the root level. And they ignore XDG [2] by persistently creating ~/snap in your home directory. I've heard Flatpak is better in this regard. I'm sure it could help with application delivery so long as it's constrained to that. I don't want half of my standard libraries or utilities suddenly becoming sandboxed. For full blown applications sandboxing would be welcomed. [1]: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html [2]: https://specifications.freedesktop.org/basedir-spec/basedir-spec-0.6.html https://specifications.freedesktop.org/basedir-spec/basedir-...

Thaxll 8y ago
Does it matters?
- deadbunny 8y ago
  Do standards matter? Yes.
  - moocowtruck 8y ago
    depends if they are holding back a better future, then no
akerro 8y ago
They just create ~/.var if you install program for single user, if as root it goes somewhere to /usr/share
lathiat 8y ago
Flatpak uses /app so I’m not sure how it’s really “better” Problem is they both need to create an area with a full separate file system which doesn’t really fit in with the FHS.
- cpburns2009 8y ago
  An /app isn't any better. If they insist on having a fully realized file-system, they can put it under /opt. Or, they could use symlinks to construct it under /run/{app,snap} similar to a chroot setup.
  - vetinari 8y ago
    /app is not visible on the host system, only inside the container. It is chroot on steroids.
    - cpburns2009 8y ago
      I don't mind that behavior.
- alexlarsson 8y ago
  /app is never visible on the host though
- vetinari 8y ago
  For flatpak, the installed apps go to /var/lib/flatpak for system-wide, ~/.local/share/flatpak for user-specific. Then there's the question of app-created data, that would normally go into some dot-directory. Flatpak by default redirects all XDG dirs into ~/.var/app/${appid}, but as a part of the required permissions, the apps can request access to the user homedir or specific subfolders. Some apps abuse it. Yes, I do mind, when an app liters into ~/Documents/. I'm looking at you, Viber.

Thaxll 8y ago

Does it matters?

deadbunny 8y ago
Do standards matter? Yes.
- moocowtruck 8y ago
  depends if they are holding back a better future, then no

akerro 8y ago

They just create ~/.var if you install program for single user, if as root it goes somewhere to /usr/share

lathiat 8y ago

Flatpak uses /app so I’m not sure how it’s really “better” Problem is they both need to create an area with a full separate file system which doesn’t really fit in with the FHS.

cpburns2009 8y ago
An /app isn't any better. If they insist on having a fully realized file-system, they can put it under /opt. Or, they could use symlinks to construct it under /run/{app,snap} similar to a chroot setup.
- vetinari 8y ago
  /app is not visible on the host system, only inside the container. It is chroot on steroids.
  - cpburns2009 8y ago
    I don't mind that behavior.
alexlarsson 8y ago
/app is never visible on the host though
vetinari 8y ago
For flatpak, the installed apps go to /var/lib/flatpak for system-wide, ~/.local/share/flatpak for user-specific. Then there's the question of app-created data, that would normally go into some dot-directory. Flatpak by default redirects all XDG dirs into ~/.var/app/${appid}, but as a part of the required permissions, the apps can request access to the user homedir or specific subfolders. Some apps abuse it. Yes, I do mind, when an app liters into ~/Documents/. I'm looking at you, Viber.