Opened 14 years ago

Closed 14 years ago

#27563 closed update (fixed)

libnotify update to 0.5.2

Reported by: markus.doits@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: haspatch Cc:
Port: libnotify

Description

My macports jsut wanted to install zenity on an "upgrade outdated" (don't ask me why), and compiling this always failed. Nailed it down to libnotify 0.4.5 which did not have a required symbol for zenity. Therefore I updated libnotify to 0.5.2 and zenity compiled fine (didn't try higher than 0.5.2 because it worked with zenity). Here are the diffs for the update.

One thing not in diffs: I changed the sources-location on my build, too (since the src for 0.5.2 is not on any mirror). So to have the patch working either the sources-location must be changed to

ftp://ftp.gnome.org/pub/GNOME/sources/libnotify/0.5/

or libnotify-0.5.2.tar.bz2 must be put on the mirrors.

I don't know if the update breaks anything, it just got me to compile zenity fine...

Attachments (3)

Portfile.diff (931 bytes) - added by markus.doits@… 14 years ago.
patch.diff (737 bytes) - added by markus.doits@… 14 years ago.
for the patch in files/
libnotify-0.6.0.diff (2.3 KB) - added by ryandesign (Ryan Carsten Schmidt) 14 years ago.
update to 0.6.0, which requires gtk3

Download all attachments as: .zip

Change History (14)

comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Port: libnotify added
Type: enhancementupdate

comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Perhaps you have winetricks installed? I recently added a zenity dependency to winetricks.

Changed 14 years ago by markus.doits@…

Attachment: Portfile.diff added

Changed 14 years ago by markus.doits@…

Attachment: patch.diff added

for the patch in files/

comment:3 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

I would guess that libnotify version numbering conventions hold that odd-numbered versions (0.5.x, 0.7.x) are development versions. So we should instead update to the latest stable version, which looks like 0.6.0.

comment:4 in reply to:  2 Changed 14 years ago by markus.doits@…

Replying to ryandesign@…:

Perhaps you have winetricks installed? I recently added a zenity dependency to winetricks.

yes, good hint. That's the reason.

comment:5 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… removed
Keywords: haspatch added
Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

comment:6 in reply to:  3 ; Changed 14 years ago by markus.doits@…

Replying to ryandesign@…:

I would guess that libnotify version numbering conventions hold that odd-numbered versions (0.5.x, 0.7.x) are development versions. So we should instead update to the latest stable version, which looks like 0.6.0.

just tried it, but looks like 0.6.0 requires gtk3

:info:configure checking for GTK3... configure: error: Package requirements (gtk+-3.0) were not met:
:info:configure 
:info:configure No package 'gtk+-3.0' found
:info:configure 
:info:configure Consider adjusting the PKG_CONFIG_PATH environment variable if you
:info:configure installed software in a non-standard prefix.
:info:configure 
:info:configure Alternatively, you may set the environment variables GTK3_CFLAGS
:info:configure and GTK3_LIBS to avoid the need to call pkg-config.
:info:configure See the pkg-config man page for more details.
:info:configure 

Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: libnotify-0.6.0.diff added

update to 0.6.0, which requires gtk3

comment:7 in reply to:  6 ; Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to markus.doits@…:

just tried it, but looks like 0.6.0 requires gtk3

I just discovered that too. So we cannot update to 0.6.0. And we cannot update to 0.5.x because it is a development version.

The libnotify 0.4.5 currently in the ports tree builds fine for me. If you're having trouble building it, perhaps you could clean and try again, and if it still fails, attach the main.log and maybe we can get that working for you?

comment:8 in reply to:  7 Changed 14 years ago by markus.doits@…

Replying to ryandesign@…:

Replying to markus.doits@…: The libnotify 0.4.5 currently in the ports tree builds fine for me. If you're having trouble building it, perhaps you could clean and try again, and if it still fails, attach the main.log and maybe we can get that working for you?

libnotify 0.4.5 builds fine fore me, too, but zenity+quartz does not with it (should be discussed in another ticket). But the solution for zenity+quartz is to upgrade libnotify to 0.5.2. I'll open another ticket for zenity if you like.

comment:9 Changed 14 years ago by markus.doits@…

zenity ticket at #27564

comment:10 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Ah, +quartz; I haven't used that.

From the NEWS file in the libnotify 0.6.0 distfile I see:

NEW in 0.6.0:
==============

The 0.5.1 release included changes that should not have been made on a
stable branch.  It should have been a 0.6 series release.  So here it is.

- Fixed #623096 Fix notify_get_server_info results


NEW in 0.5.1:
==============
- Remove explicit GTK+ 2.x linking, so that libnotify can link against
  both GTK+ 2.x or GTK+ 3.x

What I learn from this is:

  • 0.5.x is a stable branch after all
  • 0.5.x can use gtk2 or gtk3 (You demonstrated 0.5.2 could use gtk2)
  • there is no entry for 0.5.2

From the NEWS file in the libnotify 0.5.2 distfile I see:

NEW in 0.5.2:
==============

Note that the 0.5.1 release was released from the 0.6 branch in error.
Sorry about that.

- Fixed #623096, Use correct variable in NULL check
- Added a macro NOTIFY_CHECK_VERSION

So I guess that means we can update to 0.5.2 after all.

I incorrectly guessed they used the odd-number-is-unstable rule, based on experience with other GNOME software (like gtk2, glib2, and pango), and I could not find a libnotify web site or release announcements from which to learn their actual policies.

comment:11 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed

Updated to 0.5.2 in r74098.

Note: See TracTickets for help on using tickets.