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

[Jonathan Nieder]

Hi,

Jeremy Bicha wrote:
> On Thu, Sep 13, 2018 at 4:40 PM Santiago Vila <sanvila at unex.es> wrote:

>> What I said is that no sane package in Debian/main should need to put
>> files directly in /etc/opt. That's an oddity, a very unorthodox thing,
>> it would be like a Debian package in main putting stuff directly in /opt.
>
> chrome-gnome-shell (in this case) is an addon for the Google Chrome
> web browser. Since Chrome installs to /opt/ (which is encouraged by
> FHS), /etc/opt/ is the only standards-compliant location for
> chrome-gnome-shell to ship the configuration files it needs to provide
> its core functionality.
>
> There is no reason this functionality cannot be offered in Debian. We
> got complaints when we supported other browsers but not Google Chrome.

Since Google Chrome is not part of Debian, shouldn't this
functionality be offered in contrib, not Debian?

[...]
>                                                              But if
> that can't be done, I think we would be happy enough to apply a patch
> to implement the trigger workaround.

For what it's worth (especially since this is about integrating with a
non-Debian package), makes sense to me.

Thanks,
Jonathan