-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 03/06/14 08:08 AM, Tom Wijsman wrote: > On Tue, 3 Jun 2014 07:35:42 -0400 Rich Freeman <ri...@gentoo.org> > wrote: > >> This probably could have used a news item, as the change impacts >> both stable and ~arch users. > > Are we going to write a news item every time systemd acquires a > new mandatory relationship with a reverse dependency? > >> They need to do an "emerge -1 sys-power/upower-pm-utils" to >> actually get the new package, > > But the user doesn't want systemd; so, then why does the user have > to perform a manual step every time that systemd has an > acquirement?
That's easy -- we don't have a way to do vdb updates that will split a package, only move a package. And since this isn't a package move (as the original package still exists) we can't leverage that. > >> otherwise portage is going to try to switch them from udev to >> systemd, > > There is the problem, the user doesn't want systemd; so, why is > Portage (regardless of a systemd mask) trying to bring it to the > user anyway? > >> since packages like kdelibs list upower first, and portage has no >> way of knowing that this is a big change. > > And this is where you can make Portage smarter. > > http://www.funtoo.org/Flavors_and_Mix-ins > > We don't have to go through all this if you had a "no-systemd" > mix-in, where you could simply make out the choices in favor of the > user instead of having to document and announce them all over the > place. > > That mix-in could do something like masking the new upower that > depends on systemd; when doing so, no more blockers all over the > place. > Technically we could do this via a systemd profile too -- ie, mask new upower everywhere but systemd profiles, and in systemd profile mask upower-pm-utils. However, that doesn't get around the actual need to - --unmerge upower and emerge upower-pm-utils (or hopefully just do the latter as a soft-block will do the unmerge?) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlONzPEACgkQ2ugaI38ACPDI5AD/eEbk4156UrMNHmCPIA+xwNfe nlGC5pnZ3Zs0gu/88EAA/A9hNlNfGzhqorE+8cEz3lkTVuxxq8gv++7Ogm0zY8DU =I7Mw -----END PGP SIGNATURE-----
