From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-settings-daemon/
Date: Tue, 25 Sep 2018 20:46:44 +0000 (UTC) [thread overview]
Message-ID: <1537908391.83d52f2cca54f7835bbe8f7f91b1b1d198222c85.leio@gentoo> (raw)
commit: 83d52f2cca54f7835bbe8f7f91b1b1d198222c85
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Tue Sep 25 20:46:31 2018 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Tue Sep 25 20:46:31 2018 +0000
URL: https://gitweb.gentoo.org/proj/gnome.git/commit/?id=83d52f2c
gnome-base/gnome-settings-daemon: add glib-utils build dep, remove sed dep
sed is always guaranteed from system packages
Package-Manager: Portage-2.3.49, Repoman-2.3.11
gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.26.2-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.26.2-r1.ebuild b/gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.26.2-r1.ebuild
index cced7d8b..0d45c1d0 100644
--- a/gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.26.2-r1.ebuild
+++ b/gnome-base/gnome-settings-daemon/gnome-settings-daemon-3.26.2-r1.ebuild
@@ -76,13 +76,13 @@ RDEPEND="${COMMON_DEPEND}
!<gnome-base/gnome-session-3.25.4
"
DEPEND="${COMMON_DEPEND}
- cups? ( sys-apps/sed )
test? (
${PYTHON_DEPS}
$(python_gen_any_dep 'dev-python/pygobject:3[${PYTHON_USEDEP}]')
$(python_gen_any_dep 'dev-python/dbusmock[${PYTHON_USEDEP}]')
gnome-base/gnome-session )
dev-libs/libxml2:2
+ dev-util/glib-utils
sys-devel/gettext
>=dev-util/intltool-0.40
virtual/pkgconfig
next reply other threads:[~2018-09-25 20:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 20:46 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-25 20:27 [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-settings-daemon/ Mart Raudsepp
2018-09-25 20:27 Mart Raudsepp
2018-09-25 20:27 Mart Raudsepp
2018-09-25 17:51 Mart Raudsepp
2018-05-06 15:16 Sobhan Mohammadpour
2018-02-14 19:44 Sobhan Mohammadpour
2018-01-12 13:11 Dennis Lamm
2015-10-12 20:34 Ole Reifschneider
2015-05-12 19:31 Gilles Dartiguelongue
2014-12-22 23:50 Gilles Dartiguelongue
2014-11-23 22:28 Gilles Dartiguelongue
2014-10-26 16:55 Gilles Dartiguelongue
2014-10-15 22:26 Gilles Dartiguelongue
2014-04-20 18:17 Gilles Dartiguelongue
2014-02-12 20:58 Gilles Dartiguelongue
2013-12-18 22:49 Gilles Dartiguelongue
2012-12-25 21:45 Gilles Dartiguelongue
2012-11-18 19:33 Gilles Dartiguelongue
2012-09-27 7:53 Alexandre Rostovtsev
2012-09-22 15:54 Nirbheek Chauhan
2012-09-21 0:27 Nirbheek Chauhan
2012-05-24 7:49 Alexandre Restovtsev
2011-10-09 17:43 Alexandre Restovtsev
2011-06-28 3:44 Alexandre Restovtsev
2011-06-24 17:35 Alexandre Restovtsev
2011-05-30 17:43 Nirbheek Chauhan
2011-04-27 22:22 Gilles Dartiguelongue
2011-04-08 10:52 Gilles Dartiguelongue
2011-04-06 13:57 Nirbheek Chauhan
2011-04-05 0:57 Nirbheek Chauhan
2011-03-26 1:58 Nirbheek Chauhan
2011-03-23 5:20 Nirbheek Chauhan
2011-03-09 11:34 Nirbheek Chauhan
2011-03-04 14:57 Nirbheek Chauhan
2011-02-28 20:25 Nirbheek Chauhan
2011-02-22 0:31 Nirbheek Chauhan
2011-02-12 9:30 Nirbheek Chauhan
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=1537908391.83d52f2cca54f7835bbe8f7f91b1b1d198222c85.leio@gentoo \
--to=leio@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