Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

switch from Log::Dispatch::Gtk2::Notify to Log::Dispatch::Desktop::Notify #1

Merged
merged 1 commit into from May 9, 2017

Conversation

mmitch
Copy link

@mmitch mmitch commented Apr 12, 2017

Basically, both modules modules do the same: They connect to a Desktop Notification Server to display notifications.

Log::Dispatch::Gtk2::Notify depends on Gtk2::Notify which fails to install for about 5 years now because of incompatible changes in libnotify (see https://rt.cpan.org/Public/Dist/Display.html?Name=Gtk2-Notify).

Log::Dispatch::Desktop::Notify depends on Desktop::Notify instead which seems to work fine.

The fallback to Log::Dispatch::Null because of a missing $DISPLAY or Dbus session is done automatically by Log::Dispatch::Desktop::Notify.

…tify

Basically, both modules modules do the same: They connect to a Desktop
Notification Server to display notifications.

Log::Dispatch::Gtk2::Notify depends on Gtk2::Notify which fails to
install for about 5 years now because of incompatible changes in
libnotify.

Log::Dispatch::Desktop::Notify depends on Desktop::Notify instead
which seems to work fine.

The fallback to Log::Dispatch::Null because of a missing $DISPLAY or
Dbus session is done automatically by Log::Dispatch::Desktop::Notify.
@karenetheridge karenetheridge merged commit e1e060a into karenetheridge:master May 9, 2017
@karenetheridge
Copy link
Owner

merged and released, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants