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#29874 - [awesome] Split naughty into separate package?

Attached to Project: Community Packages
Opened by Ezekiel Sulastin (ZekeSulastin) - Sunday, 13 May 2012, 16:12 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 15 May 2012, 18:57 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

As noted in this thread (https://bbs.archlinux.org/viewtopic.php?id=141443), some people may want to use awesome with a separate notification-daemon. However, awesome currently provides this due to the notification module naughty; this is great if you just want to use that, but as noted in that thread it can lead to excess hassle if you want to use something else in its place.

Upstream ships everything in one big happy family, but would it be feasible to split the package here, make naughty an optdepend of awesome, and have naughty provide notification-daemon?
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Tuesday, 15 May 2012, 18:57 GMT
Reason for closing:  Won't implement
Comment by Sébastien Luttringer (seblu) - Monday, 14 May 2012, 09:04 GMT
I answered in the BBS. We don't need to split packages to be able to use another notification-daemon with naugthy shiped inside awesome.
Provide notification-daemon, doesn't conflict with other package also provide it, without force conflicts.

Loading...