linux-traipu team mailing list archive

[Avamander <1887804@xxxxxxxxxxxxxxxxxx>]

> I don't think the specification¹ mandates how folders should be
structured under $XDG_DATA_HOME and $XDG_CONFIG_HOME.

`$XDG_CONFIG_HOME/$SOFTWARE_NAME` is the de facto way, snap ignores it.
Technically, yes, you're absolutely free to use hashes instead of your
software's name when you store things in the configuration folder,
really doesn't mean it's a good idea.

> Hopefully snapd behaves (mostly) the same on all supported
distributions, so distro-hopping shouldn't be a concern either.

You're making three assumptions. That snap will behave the same across
distributions, that snap is supported on different distributions at all,
and that someone even wants to install the snap package. All of them are
frankly really bad assumptions and just cause people pain.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/1887804

Title:
  chromium-browser does not follow XDG base directory specification

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Currently Chromium does not follow the XDG base directory
  specification which means that the cache and configuration folder
  aren't properly used.

  This causes the issue that it's nearly impossible to properly migrate
  or back up Chromium configuration (between computers) and it makes for
  example mounting cache as tmpfs or wiping it very very difficult.

  I felt those both immensely when trying to migrate my home folder,
  gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder]
  (and ~/snap itself is also not XDG base directory specification
  compliant, shame!).

  There's also the issue that the previous configuration that is located
  properly, isn't migrated by the migrational package.

  In order to fix this bug, it would require making the snap package
  follow the XDG base directory specification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions