Re: [PATCH 1/3] libnotify3: remove the recipe

[Tanu Kaskinen <tanuk@iki.fi>]

On Wed, 2015-08-26 at 13:07 +0300, Alexander Kanavin wrote:
> 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


This last comment seems to be out of date after this patch.

-- 
Tanu