Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16496 - [awesome] does not provide [notification-daemon]

Attached to Project: Community Packages
Opened by Ben Kuhn (bkuhn) - Wednesday, 07 October 2009, 01:22 GMT
Last edited by Ronald van Haren (pressh) - Monday, 09 November 2009, 21:36 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

The `awesome' window manager's library `naughty' provides an implementation of the notification-daemon specification (or whatever it's called). Thus the package should provide notification-daemon.

Present in awesome through 3.3.4-1.

Steps to reproduce:
Install the package.
This task depends upon

Closed by  Ronald van Haren (pressh)
Monday, 09 November 2009, 21:36 GMT
Reason for closing:  Not a bug
Additional comments about closing:  not sure about the reason for closing here, but the original report was not valid, hence 'not a bug'...

the notification-deamon provides line is removed in awesome 3.4.1-1 again
Comment by Ben Kuhn (bkuhn) - Wednesday, 07 October 2009, 01:25 GMT
Oops, apparently the interface to attach this to the `community packages' project was too hard for me to handle. My apologies; can the report be moved?
Comment by Dan Griffiths (Ghost1227) - Sunday, 08 November 2009, 20:51 GMT
It has been brought up that this causes conflicts for users with multiple WMs setup, resulting in the need for building everything by hand. Is there a better way to handle this?
Comment by Ronald van Haren (pressh) - Monday, 09 November 2009, 08:39 GMT
well, imo it is quite easy. If awesome provides ALL functionality of notification-daemon AND can also work as a drop in replacement of it, then let have it in notification-deamon in provides.
In all other cases where it only provides a subset of all features or does not work as a drop in replacement, then don't.

So if I understand correctly it does not work as a drop in replacement?
Comment by Ben Kuhn (bkuhn) - Monday, 09 November 2009, 18:06 GMT
No. Awesome is a window manager which also implements the notification-daemon specification. If a user would like to use another window manager, then awesome would not be a suitable replacement for notification-daemon.

However, it is perfectly possible to run programs that depend on notification-daemon with only awesome installed and no notification-daemon. I thought that that was the meaning of `provides`, but apparently not. Sorry for causing problems.

With this in mind, what should I do if I want to run programs that depend on notification-daemon but not install notification-daemon itself? Just pacman -rd notification-daemon? It seems like there should be a better way.
Comment by Ronald van Haren (pressh) - Monday, 09 November 2009, 21:13 GMT
If you really do not want to have it installed you can use ABS for those packages that depend on it, there are only few of them so it should be workable.


notification-deamon is however a gnome-tool, so a package requiring that probably already installs most if the deps of notification-deamon if I'm correct. notification-deamon itself is only 0.33Mb installed.

Either way, I'll remove the dependency from the package again.

Loading...