libnotify Lion conflict

[carbncl@…]

It is a known issue, since there are changesets related explaining the problem and even suggesting a (dangerous) workaround. See r79720

I didn't found any tickets on trac related to "track" this one. So here is this ticket.

(If I missed an existing ticket, sorry for the inconvenience)

[ryandesign (Ryan Carsten Schmidt)]

The Cc field must contain complete email addresses.

Do not set the Milestone field for port tickets.

[mmpestorich (Mike M Pestorich)]

Cc Me!

[drkp (Dan Ports)]

Renamed the dylib to libnotify_gnome and re-enabled build on Lion in r85515; revbumped dependents in r85516

[jeremyhu (Jeremy Huddleston Sequoia)]

NO!

[jeremyhu (Jeremy Huddleston Sequoia)]

I fixed this in 10.6.2. The correct fix is to have libnotify require 10.6.2

[jeremyhu (Jeremy Huddleston Sequoia)]

r85521 r85522

[mshappe@…]

This fix yields a new issue:

--->  Dependencies to be installed: libnotify
Error: Target org.macports.activate returned: can't read "os.minor": no such variable
Error: Failed to install libnotify

[carbncl@…]

Sorry for this obviously off-topic comment, but a question came to my mind and I'm pretty sure someone from there will be able to answer, and I have no idea where else I should ask.

Is libnotify useless on OSX?

AFAIK it is a dbus pop-up notification library on Linux, but I doubt there is some magical bridge to Growl in it... (or else) So except to satisfy a package dependency, my guess is this package is useless, and maybe should be removed from any port capable of ignoring it? (like it was removed on deluge few days ago after my request...)

[jeremyhu (Jeremy Huddleston Sequoia)]

Sorry, I committed before testing it because I didn't want the version that was there to infect too many systems. I fixed it. I can't believe we don't have os.minor ... =/

r85583

[cooljeanius (Eric Gallager)]

Cc Me!