From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH 1/3] libnotify3: remove the recipe
Date: Wed, 26 Aug 2015 13:07:00 +0300 [thread overview]
Message-ID: <1440583622-11664-1-git-send-email-alexander.kanavin@linux.intel.com> (raw)
libnotify 0.7.6 is now provided in oe-core
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
meta-gnome/recipes-gnome/libnotify/libnotify3_0.7.3.bb | 16 ----------------
meta-gnome/recipes-gnome/nautilus/nautilus3_3.2.1.bb | 2 +-
2 files changed, 1 insertion(+), 17 deletions(-)
delete mode 100644 meta-gnome/recipes-gnome/libnotify/libnotify3_0.7.3.bb
diff --git a/meta-gnome/recipes-gnome/libnotify/libnotify3_0.7.3.bb b/meta-gnome/recipes-gnome/libnotify/libnotify3_0.7.3.bb
deleted file mode 100644
index b66fe97..0000000
--- a/meta-gnome/recipes-gnome/libnotify/libnotify3_0.7.3.bb
+++ /dev/null
@@ -1,16 +0,0 @@
-SUMMARY = "Send desktop notifications to a notification daemon"
-SECTION = "libs"
-LICENSE = "LGPLv2.1"
-LIC_FILES_CHKSUM = "file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34"
-
-DEPENDS = "dbus gtk+3"
-
-# conflicts with libnotify, mixing them in build breaks couple of packages
-EXCLUDE_FROM_WORLD = "1"
-
-BPN = "libnotify"
-
-inherit gnome lib_package
-
-SRC_URI[archive.md5sum] = "d20676bde7bd2d276508d019dc7276f1"
-SRC_URI[archive.sha256sum] = "322541fdf276eb803686df81763a5186af041b2ee3e9cc5fa1dc86c550388c88"
diff --git a/meta-gnome/recipes-gnome/nautilus/nautilus3_3.2.1.bb b/meta-gnome/recipes-gnome/nautilus/nautilus3_3.2.1.bb
index 1acf8d3..586d1d9 100644
--- a/meta-gnome/recipes-gnome/nautilus/nautilus3_3.2.1.bb
+++ b/meta-gnome/recipes-gnome/nautilus/nautilus3_3.2.1.bb
@@ -8,7 +8,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=f08a446809913fc9b3c718f0eaea0426 \
PR = "r4"
-DEPENDS = "libnotify3 gtk+3 libunique gvfs librsvg libexif gnome-desktop3"
+DEPENDS = "libnotify gtk+3 libunique gvfs librsvg libexif gnome-desktop3"
# optional: tracker
# needs libnotify3 which conflicts with libnotify, mixing them in build breaks couple of packages
--
2.1.4
next reply other threads:[~2015-08-26 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 10:07 Alexander Kanavin [this message]
2015-08-26 10:07 ` [PATCH 2/3] gnome: add explicit bz2 compress type to older packages Alexander Kanavin
2015-08-26 10:07 ` [PATCH 3/3] iso-codes: remove the recipe due to its move to oe-core Alexander Kanavin
2015-08-26 10:40 ` [PATCH 1/3] libnotify3: remove the recipe Tanu Kaskinen
2015-08-26 10:59 ` Alexander Kanavin
2015-08-26 18:01 ` Andreas Müller
2015-08-27 8:23 ` Paul Eggleton
2015-08-27 10:49 ` Andreas Müller
2015-08-27 11:00 ` Paul Eggleton
2015-08-28 6:11 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2015-09-07 11:22 Alexander Kanavin
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=1440583622-11664-1-git-send-email-alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.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