Bug#888549: Bug#888243: Bug#888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant

[Santiago Vila]

On Thu, Sep 13, 2018 at 01:23:32PM -0400, Jeremy Bicha wrote:

> References
> ----------------
> [...]
> - https://bugs.debian.org/93390

Are you serious?

Such bug was in 2001-04-10, but in 2001-11-09 I modified base-files
to provide the opt directories, this is from the changelog:

base-files (2.2.14) unstable; urgency=low

  * Created /opt, /etc/opt and /var/opt in the first install.
    They are mentioned in FHS 2.1 and required in FHS 2.2 (Closes: #118505).

You can check that those directories exist in any newly installed Debian system.

Creating directories in the postinst is a completely acceptable way to
provide FHS compliance, and in fact, it is sometimes necessary to
accomodate for mount points and similar things, see this changelog
entry for example:

base-files (7.7) unstable; urgency=low

  * The directory /mnt is not included inside base-files.deb anymore.
    Instead, it is created by postinst the very first time base-files
    is installed (by debootstrap), or when upgrading from an earlier
    base-files version. This should make the usual upgrade at every point
    release to work even if /mnt is a stale mount point. Closes: #763405.


So, to summarize again: No, this is not a bug in base-files. I'm very
sorry that this implementation detail causes trouble for you, but I
firmly believe that whatever problem you have with it does not require a
modification in base-files to be solved, or a restriction in the freedom
to remove a directory when you don't need it.

Can we reassing this already, please?

Thanks.