public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: UPower upstream (git master) and 0.99 release -> No sys-power/pm-utils support anymore
Date: Tue, 03 Jun 2014 11:40:33 +0000	[thread overview]
Message-ID: <2990845.EWIttsqmb4@andromeda> (raw)
In-Reply-To: <5389BA4C.8040106@gentoo.org>

On Saturday, May 31, 2014 02:17:32 PM Samuli Suominen wrote:
> On 31/05/14 05:47, Steven J. Long wrote:
> > On Tue, May 27, 2014 at 09:57:01AM +0300, Samuli Suominen wrote:
> >> On 27/05/14 08:34, Michał Górny wrote:
> >>> Dnia 2014-05-26, o godz. 23:15:34
> >>> 
> >>> Samuli Suominen <ssuominen@gentoo.org> napisał(a):
> >>>> UPower upstream removed sys-power/pm-utils support from 0.99 release
> >>>> (currently unkeyworded in tree), as in, from current git master.
> >>> 
> >>> Don't worry. Looking at the past, I can guess this is only a temporary
> >>> inconvenience. I'm pretty sure upower will be discontinued soon
> >>> and replaced with systemd-powerd or something :D.
> >> 
> >> That's more or less what they already did, they forced eg.
> >> xfce4-power-manager upstream
> >> to move the deleted pm-utils code from upower directly to the power
> >> manager (application)
> >> itself, likewise for xfce4-session
> >> Which means applications will now need to duplicate the pm-utils related
> >> code per application
> >> basis
> >> So I expect upower to be more or less dead for everything but systemd
> >> users, except for
> >> those upstreams that will actually follow the Xfce path and do the
> >> duplication
> >> Yet, still, small portition of the code is still 'generic', so
> >> xfce4-power-manager will still need
> >> both, upower, even 0.99, and then pm-utils, depending on the version,
> >> codepath is selected
> >> 
> >> This was sort of expected, since pm-utils has been abandoned for ~5
> >> years now at upstream,
> >> so nobody is maintaining non-systemd related power management tools
> >> anymore, and
> >> falling back to eg. manual laptop-mode-tools, acpid, etc. usage will be
> >> necessary again,
> >> it's like going back to 90s for non-systemd users :P
> > 
> > I can't believe I'm reading that from a distro-developer. Basically this
> > entire thread is "systemd is deprecating the existing tools, so let's dump
> > them and half our userbase back to the 90s, isn't that a great thing?"
> 
> Then you misunderstood. Notice the ":P" as an indicator of sarcasm.
> I've already created sys-power/upower-pm-utils where the sys-power/pm-utils
> 0.9 git branch will continue to live.

Would have been nice to fix all the dependencies BEFORE marking the systemd-
depending "sys-power/upower-pm-utils" stable.

--
Joost


  reply	other threads:[~2014-06-03  9:41 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 20:15 [gentoo-dev] UPower upstream (git master) and 0.99 release -> No sys-power/pm-utils support anymore Samuli Suominen
2014-05-26 20:21 ` [gentoo-dev] " Samuli Suominen
2014-05-27  5:34 ` [gentoo-dev] " Michał Górny
2014-05-27  6:57   ` Samuli Suominen
2014-05-31  2:47     ` [gentoo-dev] " Steven J. Long
2014-05-31 11:17       ` Samuli Suominen
2014-06-03 11:40         ` J. Roeleveld [this message]
2014-06-03 11:25           ` Samuli Suominen
2014-06-03 11:35             ` Rich Freeman
2014-06-03 12:08               ` Tom Wijsman
2014-06-03 12:24                 ` Samuli Suominen
2014-06-03 12:52                   ` Tom Wijsman
2014-06-03 13:04                   ` Rich Freeman
2014-06-03 13:20                     ` Tom Wijsman
2014-06-03 13:28                       ` Samuli Suominen
2014-06-03 13:40                         ` Tom Wijsman
2014-06-03 13:46                           ` Samuli Suominen
2014-06-03 13:53                             ` Rich Freeman
2014-06-03 14:05                               ` Tom Wijsman
2014-06-03 14:09                                 ` Rich Freeman
2014-06-03 15:48                                   ` Tom Wijsman
2014-06-03 15:52                                     ` Ciaran McCreesh
2014-06-03 16:04                                       ` Tom Wijsman
2014-06-03 14:12                               ` Samuli Suominen
2014-06-03 14:45                                 ` Chí-Thanh Christopher Nguyễn
2014-06-03 14:49                                   ` Samuli Suominen
2014-06-03 14:57                                     ` Chí-Thanh Christopher Nguyễn
2014-06-03 16:09                                       ` Tom Wijsman
2014-06-03 19:18                                   ` J. Roeleveld
2014-06-03 19:14                             ` J. Roeleveld
2014-06-03 13:29                       ` Rich Freeman
2014-06-03 13:41                         ` Tom Wijsman
2014-06-03 13:26                 ` Ian Stakenvicius
2014-06-03 14:03                   ` Tom Wijsman
2014-06-03 23:55             ` Patrick Lauer
2014-06-04  0:24               ` Tom Wijsman
2014-06-04  0:44                 ` Patrick Lauer
2014-06-04  6:58                   ` Tom Wijsman
2014-06-04  1:20                 ` Greg Woodbury
2014-06-04  8:11                   ` Olav Vitters
2014-06-04  1:45                 ` Off-list: " Alan McKinnon
2014-06-04  6:11                 ` Duncan
2014-05-27  8:19   ` [gentoo-dev] " Alexey Shvetsov
2014-05-27  8:19     ` Alexey Shvetsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2990845.EWIttsqmb4@andromeda \
    --to=joost@antarean.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox