Some history first:
When sys-fs/udisks and sys-power/upower was introduced to Portage, they
only had handful of consumers,
and there was no sys-apps/systemd in Portage
They were non problematic packages and could be considered as wrappers
that linked desktops to udev -related
functionality
But, now, upower upstream writes code only with systemd in mind, dropped
hibernate/suspend without any
consideration to non-systemd users
And, Portage doesn't understand || ( ) dependencies anymore wrt
http://bugs.gentoo.org/show_bug.cgi?id=515230
And, people started using local USE flags "udisks" and "upower" despite
being advised against it
And, more people are requesting sys-fs/udisks and sys-power/upower to be
moved away from USE="udev" to
these 2 separate flags, like http://bugs.gentoo.org/show_bug.cgi?id=516380
These 2 flags are already enabled by default in the desktop profile
target, just like USE="udev" is
So, I propose:
upower with short generic description of "Support for power management"
udisks with short generic description of "Support for storage management"
These packages use them already, but a lot more will follow:
[+ D ] upower
kde-base/kdelibs: Use upower for power management
[+ B] (4/4.12) 4.12.5 [gentoo]
[+ B] (4/4.13) 4.13.0 [gentoo]
[+ D ] upower
kde-misc/synaptiks: Handle mouse devices correctly across suspend and
resume with upower
[+ B] (4) 0.8.1-r2 [gentoo]
[+ B] (4) 0.8.1-r4 [gentoo]
[+ D ] upower
lxde-base/lxsession: Pull in sys-power/upower for hibernate/suspend
support
[+ ] 0.4.6.1 [gentoo]
[+ ] 0.4.9.2 [gentoo]
[+ ] 0.4.9.2-r1 [gentoo]
[+ ] 0.4.9.2-r2 [gentoo]
[+ ] 0.4.9.2-r3 [gentoo]
[+ D ] upower
net-im/telepathy-mission-control: Use sys-power/upower to detect
suspend and resume
[+ B] 5.14.0-r1 [gentoo]
[+ B] 5.14.1 [gentoo]
5.16.1 [gentoo]
[+ D ] udisks
app-emulation/wine: Support dynamic storage devices using
sys-fs/udisks
1.2.3 [gentoo]
1.3.28 [gentoo]
[+ ] 1.4 [gentoo]
[+ ] 1.4.1 [gentoo]
[+ ] 1.5.0 [gentoo]
[+ ] 1.5.1 [gentoo]
[+ ] 1.5.2 [gentoo]
[+ ] 1.5.3 [gentoo]
[+ ] 1.5.4 [gentoo]
[+ ] 1.5.5 [gentoo]
[+ ] 1.5.6 [gentoo]
[+ ] 1.5.7 [gentoo]
[+ ] 1.5.8 [gentoo]
[+ ] 1.5.9 [gentoo]
[+ ] 1.5.10-r1 [gentoo]
[+ ] 1.5.11-r1 [gentoo]
[+ ] 1.5.12-r1 [gentoo]
[+ ] 1.5.13-r1 [gentoo]
[+ ] 1.5.14-r1 [gentoo]
[+ ] 1.5.15-r2 [gentoo]
[+ ] 1.5.16-r1 [gentoo]
[+ ] 1.5.17 [gentoo]
[+ ] 1.5.18 [gentoo]
[+ ] 1.5.19 [gentoo]
[+ ] 1.5.20 [gentoo]
[+ ] 1.5.21 [gentoo]
[+ ] 1.5.22 [gentoo]
[+ ] 1.5.23-r1 [gentoo]
[+ ] 1.5.24 [gentoo]
[+ ] 1.5.25 [gentoo]
[+ ] 1.5.26 [gentoo]
[+ ] 1.5.27 [gentoo]
[+ ] 1.5.28 [gentoo]
[+ ] 1.5.29 [gentoo]
[+ ] 1.5.30 [gentoo]
[+ ] 1.5.31 [gentoo]
[+ B] 1.6 [gentoo]
[+ B] 1.6.1 [gentoo]
[+ B] 1.6.2 [gentoo]
[+ B] 1.7.0 [gentoo]
[+ B] 1.7.3 [gentoo]
[+ B] 1.7.4 [gentoo]
[+ B] 1.7.8 [gentoo]
[+ B] 1.7.9 [gentoo]
[+ B] 1.7.10 [gentoo]
[+ B] 1.7.11 [gentoo]
[+ B] 1.7.12 [gentoo]
[+ B] 1.7.13 [gentoo]
[+ B] 1.7.14 [gentoo]
[+ B] 1.7.15 [gentoo]
[+ B] 1.7.16 [gentoo]
[+ B] 1.7.17 [gentoo]
[+ B] 1.7.18 [gentoo]
[+ B] 9999 [gentoo]
[+ D ] udisks
app-leechcraft/lc-vrooby: Use sys-fs/udisks:0 for block device access
(e.g., automounting)
[+ ] 0.6.60 [gentoo]
[+ ] 0.6.65 [gentoo]
[+ ] 9999 [gentoo]
[+ D ] udisks
app-text/calibre: Add run-time dependency on sys-fs/udisks in order
to mount and unmount reading devices.
[+ B] 1.2 [gentoo]
[+ B] 1.20 [gentoo]
[+ B] 1.25 [gentoo]
[+ B] 1.29 [gentoo]
[+ B] 1.35 [gentoo]
[+ D ] udisks
gnome-base/gvfs: Enable volume monitoring using sys-fs/udisks
[+ ] 1.18.3 [gentoo]
[+ ] 1.18.3-r1 [gentoo]
[+ ] 1.20.1 [gentoo]
[+ D ] udisks
kde-base/kdelibs: Use udisks for block device access (e.g.,
automounting)
[+ B] (4/4.12) 4.12.5 [gentoo]
[+ B] (4/4.13) 4.13.0 [gentoo]
[+ D ] udisks
x11-libs/libfm: Use libfm's udisks-based volume monitor
implementation instead of using the one from gvfs
0.1.17-r1 [gentoo]
[+ ] (0/4.7.1) 1.1.4 [gentoo]
[+ ] (0/4.0.0) 1.2.0 [gentoo]
[+ ] (0/4.0.0) 9999 [gentoo]
[+ D ] udisks
xfce-extra/xfce4-power-manager: Pull in sys-fs/udisks for spindown
support
[+ B] 1.2.0-r2 [gentoo]
[+ B] 1.2.0_p20140511 [gentoo]
