Since upstream deprecated pm-utils as a hard dependency since upower-0.9.20 couldn't we make it an option by introducing the pm-utils useflag to the upower ebuild? Reproducible: Always Steps to Reproduce: 1. emerge -av upower Actual Results: pulls in pm-utils Expected Results: pm-utils should be optional
no, it shouldn't be optional on non-systemd systems, upower uses either pm-utils or systemd, and we have a USE flag 'systemd' to control this already the commit message might be a bit vague, don't let it confuse you
An exclusive usage of USE=systemd might be confusing. If I wanted to use upower without pm-utils on a openrc based system it's not intuitive and/or clear why I would have to set USE=systemd in that case. The point is that there are situations where users have to use upower but do not want or simply can not use pm-utils. Thus they don't need or want pm-utils to be installed on their systems at all. Into my mind come examples where people would like to use upower without pm-utils: - Booting from a ssd is so fast that it's not profitable to suspend at all - Resigned to use suspend because of quirky hardware Both cases apply to two of my machines. :) Nevertheless those usecases might require upower for other purposes like shutdown and reboot actions.
Created attachment 371888 [details, diff] USE=pm-utils patch - Introduces pm-utils IUSE - "--disable-deprecated" is set as a default - "--enable-deprecated" is only set if USE=pm-utils is set - Introduced softblockers for systemd and pm-utils
Created attachment 371890 [details] upower-0.9.23.ebuild Corresponding ebuild for the patch to make reviewing easier
