public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Patrice Clement" <monsieurp@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-extra/chrome-gnome-shell/
Date: Sat, 17 Sep 2016 14:44:48 +0000 (UTC)	[thread overview]
Message-ID: <1474123471.9a6b733e64a7258aa86e721457eaf0893cb6441d.monsieurp@gentoo> (raw)

commit:     9a6b733e64a7258aa86e721457eaf0893cb6441d
Author:     Yuri Konotopov <ykonotopov <AT> gmail <DOT> com>
AuthorDate: Sat Sep 10 08:59:43 2016 +0000
Commit:     Patrice Clement <monsieurp <AT> gentoo <DOT> org>
CommitDate: Sat Sep 17 14:44:31 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9a6b733e

gnome-extra/chrome-gnome-shell: version bump, remove old.

Closes: https://github.com/gentoo/gentoo/pull/2252

Signed-off-by: Patrice Clement <monsieurp <AT> gentoo.org>

 gnome-extra/chrome-gnome-shell/Manifest              |  2 +-
 ...-shell-6.2.ebuild => chrome-gnome-shell-7.ebuild} | 20 ++++++++++++++++----
 2 files changed, 17 insertions(+), 5 deletions(-)

diff --git a/gnome-extra/chrome-gnome-shell/Manifest b/gnome-extra/chrome-gnome-shell/Manifest
index 296c9c5..30a4810 100644
--- a/gnome-extra/chrome-gnome-shell/Manifest
+++ b/gnome-extra/chrome-gnome-shell/Manifest
@@ -1 +1 @@
-DIST chrome-gnome-shell-6.2.tar.xz 74668 SHA256 8686e464b1eb85e8f917607b0cd764e92a06bc9c6108e17dba6b71f058a41fe5 SHA512 8a4cf249bab8bea4551771c60f8afd16bb7ef2947f49f7abcdeb09d19305ce9d94da2b239ed38ae07da6e3a6b52c50c5562365df0573b6c7641980a2a24da9c9 WHIRLPOOL 3bf4240383dba35f6695c7e6744aaf5d98749e6d53f34ad9c0de7790c105978d96e58c7818c1a43597b63036cdae7a25842bf20b2b565af9f101d444eeb88682
+DIST chrome-gnome-shell-7.tar.xz 95952 SHA256 c91ff43ed959ed07dc0cc29b20ab21d7f0f2c3b7a49e32d2d45f361357d748f3 SHA512 cc57b9398d612a153dbc67eeb48ed3ef943985e4376b59bf683b20d230d4dd28394c2ae3b587ce3b39b9fcfeb56779473f23f27a06f7d8523f732b1e88cc6701 WHIRLPOOL 5181adf2d9e86fb314fa8bf184badc59823e66494ef0005aec7e6d4573f17eac8980c4fc4f4ad79796b36a8a7e3f08eb6d6aaec2bafdac85ed49cc09f5d65c52

diff --git a/gnome-extra/chrome-gnome-shell/chrome-gnome-shell-6.2.ebuild b/gnome-extra/chrome-gnome-shell/chrome-gnome-shell-7.ebuild
similarity index 54%
rename from gnome-extra/chrome-gnome-shell/chrome-gnome-shell-6.2.ebuild
rename to gnome-extra/chrome-gnome-shell/chrome-gnome-shell-7.ebuild
index 0d03946..69e17ff 100644
--- a/gnome-extra/chrome-gnome-shell/chrome-gnome-shell-6.2.ebuild
+++ b/gnome-extra/chrome-gnome-shell/chrome-gnome-shell-7.ebuild
@@ -8,7 +8,7 @@ PYTHON_COMPAT=( python2_7 python3_{3,4,5} )
 
 inherit cmake-utils python-single-r1
 
-DESCRIPTION="Provides integration with GNOME Shell extensions repository for Chrome browser"
+DESCRIPTION="GNOME Shell integration for Chrome/Chromium, Vivaldi, Opera browsers"
 HOMEPAGE="https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome"
 SRC_URI="mirror://gnome/sources/${PN}/${PV}/${P}.tar.xz"
 
@@ -19,15 +19,27 @@ IUSE=""
 
 REQUIRED_USE="${PYTHON_REQUIRED_USE}"
 
+DEPEND="${PYTHON_DEPS}
+	sys-apps/coreutils
+"
 RDEPEND="${PYTHON_DEPS}
 	dev-python/pygobject:3[${PYTHON_USEDEP}]
 	gnome-base/gnome-shell
 "
 
 src_configure() {
-	python_setup
-	python_fix_shebang ./connector
-
 	local mycmakeargs=( -DBUILD_EXTENSION=OFF )
 	cmake-utils_src_configure
 }
+
+src_install() {
+	# Chrome policy files should be removed with package.
+	# Otherwise it will not be possible to uninstall web extension
+	# from browser.
+	echo -n "CONFIG_PROTECT_MASK=\"" > 50"${PN}" || die
+	echo -n "/etc/chromium/policies/managed/${PN}.json " >> 50"${PN}" || die
+	echo "/etc/opt/chrome/policies/managed/${PN}.json\"" >> 50"${PN}" || die
+	doenvd 50"${PN}"
+
+	cmake-utils_src_install
+}


             reply	other threads:[~2016-09-17 14:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 14:44 Patrice Clement [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-13 17:26 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/chrome-gnome-shell/ Sam James
2022-03-13 17:26 Sam James
2022-03-13 11:54 Jakov Smolić
2022-03-12 12:08 Jakov Smolić
2022-03-11 16:16 Sam James
2021-12-28  3:11 Georgy Yakovlev
2021-03-04  0:23 Sam James
2021-02-25 12:02 Ben Kohler
2021-01-01  0:59 Michał Górny
2020-04-25 21:14 Mart Raudsepp
2020-04-25 18:04 Matt Turner
2020-02-10 11:54 Michał Górny
2020-02-09 16:25 Michał Górny
2020-01-07 17:34 Ben Kohler
2020-01-07 17:26 Ben Kohler
2019-08-03 19:04 Aaron Bauman
2019-06-20  9:20 Mikle Kolyada
2019-04-19 12:52 Michał Górny
2018-11-18  9:51 Mikle Kolyada
2018-10-16  9:18 Tobias Klausmann
2018-04-25 20:27 Thomas Deutschmann
2018-04-06 14:43 Aaron Bauman
2018-02-17 15:26 Patrice Clement
2018-02-17 15:26 Patrice Clement
2017-09-17 11:42 Sergei Trofimovich
2017-09-17 11:14 Sergei Trofimovich
2017-07-10  7:08 Sergei Trofimovich
2017-04-26 21:03 Patrice Clement
2017-04-26 21:03 Patrice Clement
2017-03-02 10:41 Agostino Sarubbo
2017-03-02 10:40 Agostino Sarubbo
2017-02-18  4:37 Michael Palimaka
2017-01-26  3:14 Mart Raudsepp
2017-01-25 11:03 Mikhail Pukhlikov
2017-01-18 10:18 David Seifert
2017-01-04 23:18 Patrice Clement
2016-09-26 11:25 Patrice Clement
2016-08-07 20:43 Patrice Clement
2016-05-18  6:30 Ian Delaney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1474123471.9a6b733e64a7258aa86e721457eaf0893cb6441d.monsieurp@gentoo \
    --to=monsieurp@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox