Date: Sat, 20 Aug 2016 21:40:46 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 212017] www/chromium should not use /usr/local/etc instead of /etc for policies and native messaging Message-ID: <bug-212017-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212017 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@FreeBSD.org Reporter: ykonotopov@gmail.com Assignee: chromium@FreeBSD.org Flags: maintainer-feedback?(chromium@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 chang= ed path to Chromium policies and Native massaging manifests (https://svn0.us-east.freebsd.org/ports/head/www/chromium/files/patch-chrom= e_common_chrome__paths.cc). This patch forces Chromium to search Policies in "/usr/local/etc/chrome/policies" instead of "/etc/chromium/policies" and Na= tive messaging manifests in "/usr/local/etc/chrome/native-messaging-hosts" inste= ad 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-h= ost-location and https://www.chromium.org/administrators/linux-quick-start). No one Chrome developer knows about this FreeBSD patch and other configurat= ion 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212017-13>