[Bug 212017] www/chromium should not use /usr/local/etc instead of /etc for policies and native messaging

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212017

            Bug ID: 212017
           Summary: www/chromium should not use /usr/local/etc instead of
                    /etc for policies and native messaging
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: chromium at FreeBSD.org
          Reporter: ykonotopov at gmail.com
          Assignee: chromium at FreeBSD.org
             Flags: maintainer-feedback?(chromium at FreeBSD.org)

Hi,

I'm not FreeBSD user, but developer of GNOME Shell integration for Chrome
extension.
Recently FreeBSD user reported that extension not works in FreeBSD.

After debugging this issue we discovered that FreeBSD uses patch that changed
path to Chromium policies and Native massaging manifests
(https://svn0.us-east.freebsd.org/ports/head/www/chromium/files/patch-chrome_common_chrome__paths.cc).

This patch forces Chromium to search Policies in
"/usr/local/etc/chrome/policies" instead of "/etc/chromium/policies" and Native
messaging manifests in "/usr/local/etc/chrome/native-messaging-hosts" instead
of "/etc/chromium/native-messaging-hosts".

In my opinion this is wrong because those locations are not documented by
Google
(https://developer.chrome.com/extensions/nativeMessaging#native-messaging-host-location
and https://www.chromium.org/administrators/linux-quick-start).
No one Chrome developer knows about this FreeBSD patch and other configuration
files locations.

If in FreeBSD those settings locations should be moved (because of some OS
policies) those changes should be sent upstream and properly documented. As for
now those silent changes lead to confusion.

-- 
You are receiving this mail because:
You are the assignee for the bug.