From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6A4A91381FA for ; Tue, 3 Jun 2014 13:26:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B3344E08FC; Tue, 3 Jun 2014 13:26:11 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C01CDE08D6 for ; Tue, 3 Jun 2014 13:26:10 +0000 (UTC) Received: from [192.168.1.130] (bas1-ottawa09-2925287741.dsl.bell.ca [174.92.89.61]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: axs) by smtp.gentoo.org (Postfix) with ESMTPSA id 6A1F733F87D for ; Tue, 3 Jun 2014 13:26:09 +0000 (UTC) Message-ID: <538DCCF1.8080904@gentoo.org> Date: Tue, 03 Jun 2014 09:26:09 -0400 From: Ian Stakenvicius User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 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 References: <5383A0E6.3020700@gentoo.org> <20140531024701.GB3828@rathaus.eclipse.co.uk> <5389BA4C.8040106@gentoo.org> <2990845.EWIttsqmb4@andromeda> <538DB0C5.6070206@gentoo.org> <20140603140850.7b69dff6@gentoo.org> In-Reply-To: <20140603140850.7b69dff6@gentoo.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: cb8084c5-035e-4142-8040-b74e4c7a992e X-Archives-Hash: aa3b131deab7f7dca60e5b86d018cd24 -----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 > 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-----