Skip to contentSkip to conversation

libnotify: add 0.5.2 and make it the default

PATCH In review Connor Abbott 3 participants 5 messages Nov 20, 2011 – Dec 5, 2011

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 libnotify: add 0.5.2 and make it the default

Versions of libnotify >= 0.6.0 have API changes that break some gnome recipes.

---
 .../recipes-gnome/libnotify/libnotify_0.5.2.bb     |   10 ++++++++++
 .../recipes-gnome/libnotify/libnotify_0.6.0.bb     |    2 ++
 2 files changed, 12 insertions(+), 0 deletions(-)
 create mode 100644 meta-gnome/recipes-gnome/libnotify/libnotify_0.5.2.bb
meta-gnome/recipes-gnome/libnotify/libnotify_0.5.2.bb new file +10 -0
new file mode 100644
index 0000000..5ce0eb6
@@ -0,0 +1,10 @@
+DESCRIPTION = "Send desktop notifications to a notification daemon"
+SECTION = "libs"
+LICENSE = "LGPLv2.1"
+LIC_FILES_CHKSUM = "file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34"
+
+DEPENDS = "dbus gtk+"
+
+inherit gnome
+SRC_URI[archive.md5sum] = "4361058ae4e28a9ffce6764e7d03acd1"
+SRC_URI[archive.sha256sum] = "1f6f1a2d6a0e009997c7ed31f6197f9bf09e9b45fb9cd54acabceea951d99062"
meta-gnome/recipes-gnome/libnotify/libnotify_0.6.0.bb +2 -0
index 45adbd7..e6c4a95 100644
@@ -5,6 +5,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34"
 
 DEPENDS = "dbus gtk+"
 
+DEFAULT_PREFERENCE = "-99"
+
 inherit gnome
 SRC_URI[archive.md5sum] = "732c9d2cd5eb6a9069264a319d330516"
 SRC_URI[archive.sha256sum] = "73b16a79bb2fed62dcf146b11c4405776cb96a09dce66379ca541da7dbd64210"
Signature · 1 line
1.7.5.4
#1 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 20-11-11 18:56, Connor Abbott schreef:

Quoted 2 lines

Versions of libnotify >= 0.6.0 have API changes that break some gnome recipes.

Which recipes are that? The only API breakage I know of is in libnoty >= 0.7.0, which is why that's called 'libnotify3'

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk7KBHAACgkQMkyGM64RGpFcmQCfXeZgqdkn76RQO6fErXYARefD 2zsAnAgBzS2HiSx1RQQ+hvW63Le66qsY
=0+pG
-----END PGP SIGNATURE-----

#2 lore raw

Sorry, I must have had the 0.7.0 headers installed and didn't realize it. Actually, that's a problem; if you build two different packages, one which requires libnotify and one which requires libnotify3, then the wrong headers can get installed in the sysroot because the packages have different names. Anyways, it appears that 0.5.2 is actually newer than 0.6.0 anyways; I'll update the commit message then.

Quoted 26 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 20-11-11 18:56, Connor Abbott schreef:

Quoted 2 lines

Versions of libnotify >= 0.6.0 have API changes that break some gnome recipes.

Which recipes are that? The only API breakage I know of is in libnoty >= 0.7.0, which is why that's called 'libnotify3'

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk7KBHAACgkQMkyGM64RGpFcmQCfXeZgqdkn76RQO6fErXYARefD 2zsAnAgBzS2HiSx1RQQ+hvW63Le66qsY
=0+pG
-----END PGP SIGNATURE-----

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#3 lore raw
Quoted 6 lines · Connor Abbott

Sorry, I must have had the 0.7.0 headers installed and didn't realize it. Actually, that's a problem; if you build two different packages, one which requires libnotify and one which requires libnotify3, then the wrong headers can get installed in the sysroot because the packages have different names. Anyways, it appears that 0.5.2 is actually newer than 0.6.0 anyways; I'll update the commit message then.

if they are incompatible and needs to live together then they should have different install locations
in sysroot for headers and libs e.g. /usr/include/libnotify2 and /usr/include/libnotify3

#4 lore raw

Well, in this case they don't, everything just intalls to /usr/include/notify. The reason is that usually, programs using libnotify hardcode that directory like this:
#include <notify/notify.h>

So it's impossible to install multiple versions at once without breakage at least without changing the library itself or all its dependencies, as I discovered.

Quoted 20 lines · Khem Raj
Quoted 2 lines · Connor Abbott

Sorry, I must have had the 0.7.0 headers installed and didn't realize it. Actually, that's a problem; if you build two different packages, one

which

Quoted 4 lines

requires libnotify and one which requires libnotify3, then the wrong headers can get installed in the sysroot because the packages have different names. Anyways, it appears that 0.5.2 is actually newer than 0.6.0 anyways; I'll update the commit message then.

if they are incompatible and needs to live together then they should have different install locations
in sysroot for headers and libs e.g. /usr/include/libnotify2 and /usr/include/libnotify3

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel