From: <kai.kang@windriver.com>
To: <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: [PATCH v2 09/15] xfce4-power-manager: 1.6.2 -> 1.6.3
Date: Tue, 16 Jul 2019 10:12:25 -0400 [thread overview]
Message-ID: <20190716141231.77957-10-kai.kang@windriver.com> (raw)
In-Reply-To: <20190716141231.77957-1-kai.kang@windriver.com>
From: Kai Kang <kai.kang@windriver.com>
* clean DEPENDS
- dbus-glib has been replaced by gdbus
- gtk+3 glib-2.0 xfconf and libxfce4util are required by libxfce4ui
which is required by xfce4-panel
Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
...power-manager_1.6.2.bb => xfce4-power-manager_1.6.3.bb} | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
rename meta-xfce/recipes-xfce/xfce4-power-manager/{xfce4-power-manager_1.6.2.bb => xfce4-power-manager_1.6.3.bb} (79%)
diff --git a/meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.2.bb b/meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.3.bb
similarity index 79%
rename from meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.2.bb
rename to meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.3.bb
index 0a44b1f5d..b03adc46b 100644
--- a/meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.2.bb
+++ b/meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.3.bb
@@ -9,11 +9,10 @@ inherit xfce distro_features_check
REQUIRED_DISTRO_FEATURES = "x11"
-DEPENDS += "gtk+3 glib-2.0 dbus-glib xfconf libxfce4ui libxfce4util libnotify \
- libxrandr virtual/libx11 libxext xfce4-panel upower libxscrnsaver"
+DEPENDS += "libnotify libxrandr virtual/libx11 libxext xfce4-panel upower libxscrnsaver"
-SRC_URI[md5sum] = "2a49be4eca78fb519984db5aae38e4ab"
-SRC_URI[sha256sum] = "66ac34b33a2021b5af04c0181dfab6e6ee2bfab0ae07ed4527ca4552a66e1c01"
+SRC_URI[md5sum] = "b5ed83dd7f30a54f95d1fae1c84fa33c"
+SRC_URI[sha256sum] = "debd8ac2409b5ac230593894b8bb668298f78bd12891623edbfc32ac87c64011"
EXTRA_OECONF = " \
--enable-network-manager \
--
2.20.0
next prev parent reply other threads:[~2019-07-16 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 14:12 [PATCH v2 00/15] Upgrade to xfce 4.14 pre2 kai.kang
2019-07-16 14:12 ` [PATCH v2 01/15] libxfce4util: 4.13.3 -> 4.13.4 kai.kang
2019-07-16 14:12 ` [PATCH v2 02/15] libxfce4ui: 4.13.5 -> 4.13.6 kai.kang
2019-07-16 14:12 ` [PATCH v2 03/15] exo: 0.12.5 -> 0.12.6 kai.kang
2019-07-16 14:12 ` [PATCH v2 04/15] xfconf: 4.13.7 -> 4.13.8 kai.kang
2019-07-16 14:12 ` [PATCH v2 05/15] thunar: 1.8.6 -> 1.8.7 kai.kang
2019-07-16 14:12 ` [PATCH v2 06/15] xfce4-session: 4.13.2 -> 4.13.3 kai.kang
2019-07-16 14:12 ` [PATCH v2 07/15] xfwm4: " kai.kang
2019-07-16 14:12 ` [PATCH v2 08/15] xfdesktop: 4.13.4 -> 4.13.5 kai.kang
2019-07-16 14:12 ` kai.kang [this message]
2019-07-16 14:12 ` [PATCH v2 10/15] xfce4-panel: 4.13.5 -> 4.13.6 kai.kang
2019-07-16 14:12 ` [PATCH v2 11/15] xfce4-dev-tools: 4.12.0 -> 4.13.0 kai.kang
2019-07-16 14:12 ` [PATCH v2 12/15] thunar-volman: 0.9.2 -> 0.9.3 kai.kang
2019-07-16 14:12 ` [PATCH v2 13/15] garcon: 0.6.2 -> 0.6.3 kai.kang
2019-07-16 14:12 ` [PATCH v2 14/15] xfce4-settings: 4.12.4 -> 4.13.7 kai.kang
2019-07-16 14:12 ` [PATCH v2 15/15] xfce4-pulseaudio-plugin: add dependency dbus-glib kai.kang
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=20190716141231.77957-10-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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