| Summary: | mail-client/claws-mail-4.3.1 (and -9999) please relax notification REQUIRED_USE | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Duncan <1i5t5.duncan> |
| Component: | Current packages | Assignee: | Bernard Cafarelli <voyageur> |
| Status: | UNCONFIRMED --- | ||
| Severity: | enhancement | CC: | kuraga333 |
| Priority: | Normal | Keywords: | PullRequest |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=950681 https://github.com/gentoo/gentoo/pull/41415 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Bug #950681 is sort of the reverse request -- for the three notification libs to REQUIRED_USE notification. I'm not sure if they require it notification to build, but the built-in notification plugins definitely don't require any of those libs, thus the request here. What do you mean by `banner plugin`? (In reply to Alexander Kurakin from comment #2) > What do you mean by `banner plugin`? Ah, seems like it's about "the banner module", https://www.claws-mail.org/plugin.php?plugin=notification (In reply to Alexander Kurakin from comment #3) > (In reply to Alexander Kurakin from comment #2) > > What do you mean by `banner plugin`? > > Ah, seems like it's about "the banner module", > https://www.claws-mail.org/plugin.php?plugin=notification Yes. (I crafted a reply with an explanation but got bugzi's "mid-air collision" warning when I went to submit. Seems you beat me to it.) Agree! Moreover, propose to drop these USE flags. See https://github.com/gentoo/gentoo/pull/41415 . |
The two "notification" plugins I actually use: * banner (for new mail notification) * systray (not actually for notification, but because its close-to-tray functionality seems to be the only way to close the claws-mail window while still keeping it running and thus continuing to timed-poll main and feeds) Both of these are build-activated by USE=notification (which toggles the build-system's notification-plugins in src_configure), but neither one require additional USE flags or depends. Unfortunately current notification REQUIRED_USE: notification? ( || ( appindicator libcanberra libnotify ) ) Then in COMMONDEPEND: notification? ( appindicator? ( dev-libs/libayatana-appindicator ) libcanberra? ( || ( media-libs/libcanberra-gtk3 media-libs/libcanberra[gtk3(-)] ) ) libnotify? ( x11-libs/libnotify ) ) Note that notification itself, and the banner and systray plugins it enables, have no deps of their own (were it not for that REQUIRED_USE). Finally in src_configure() we have only: $(use_enable notification notification-plugin) There's no independent package configuration for the three ||-required flags. So what's actually provoking this request now? I /did/ have libnotify enabled, but I'm running live-git kde-frameworks/plasma (from the kde overlay), and as one might expect from live-git, sometimes bits of it aren't entirely stable. ATM plasmashell is broken, but fortunately I can still run a kwin wayland session and use my launcher hotkeys, etc, and (short term anyway) the pretty plasmashell GUI isn't /that/ critical on its own. (And FWIW I keep the low-deps weston installed as a backup wayland compositor in case kwin_wayland itself breaks... and did have to fall back to it once for a week or so a couple years ago.) Unfortunately with USE=libnotify, claws-mail was stalling while trying to fetch messages, getting a libnotify IO error trying to talk to the broken plasmashell to notify about them. I decided I needed dependably working mail and feeds more than I needed libnotify services. So I tried to turn off libnotify and ran square into this REQUIRED_USE! Turns out removing the notifications REQUIRED_USE line from the ebuild still allows claws-mail built with USE=notification to build with its own notification plugins and the banner and systray notification plugins still work -- without stalling claws-mail message fetching due to that libnotify IO error when plasmashell breaks. So here's the bug requesting removal of the notifications REQUIRED_USE line so I can remove my local patch-out. :^)