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 1CE13138268 for ; Thu, 3 Jan 2013 02:37:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0795821C038; Thu, 3 Jan 2013 02:36:56 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BB56B21C025 for ; Thu, 3 Jan 2013 02:36:18 +0000 (UTC) Received: from [192.168.26.5] (ip98-164-195-43.oc.oc.cox.net [98.164.195.43]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id B3C8E33BDD3; Thu, 3 Jan 2013 02:36:17 +0000 (UTC) Message-ID: <50E4EEA0.60805@gentoo.org> Date: Wed, 02 Jan 2013 18:36:16 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.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, Leho Kraav Subject: Re: [gentoo-dev] emerge --depclean vs missing IUSE in older ebuild.. what exactly is right? References: <50E1ADA8.8070900@kraav.com> <20121231163444.14d8a4d5@pomiocik.lan> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 58eb7070-e0d0-411b-aa9d-4cb63775ceb6 X-Archives-Hash: 19549356b8bb5698ecbffb7ac1641407 On 01/02/2013 08:49 AM, Leho Kraav wrote: > Ok my conclusion is then that gdm-3.4.1.ebuild should be patched for [systemd?-], considering it seems otherwise fully compatible with current stable pambase. Opinions? Since gdm is using EAPI 4, sys-auth/pambase[consolekit?,systemd(-)?] seems doable. You can file a bug at http://bugs.gentoo.org to have the maintainers fix it (if they agree). -- Thanks, Zac