From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Nn1bN-0002Hz-UK for garchives@archives.gentoo.org; Thu, 04 Mar 2010 03:19:54 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1FE0BE0D39; Thu, 4 Mar 2010 03:19:52 +0000 (UTC) Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181]) by pigeon.gentoo.org (Postfix) with ESMTP id B6B81E0D25 for ; Thu, 4 Mar 2010 03:19:46 +0000 (UTC) Received: by gyg4 with SMTP id 4so936805gyg.40 for ; Wed, 03 Mar 2010 19:19:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=OTT61+OmStLp+zRvkYBgpiVU6O14z82m0qoIIesW4vU=; b=Cq1N1JCVhctivgqJn1+20AI64dswPjBnXS9XQ9LZfwiYGYouE1lBhXne8u/q6FQXT8 pli7/yEW9dHqBImyOERjXZtZ3JxoZd9ZTp06hFwsctxTRZRdNINuJKd60dyWFsJwCJXd +KWfbk0ZZNxLvS860fBUKYNApex1EXxRvShso= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=K0lLJlDb5y9HbgeSD1+f8ioJOwnrqd4MwDLx1zBuIVE7CeuzMEmtxnT2AE/T+tYpX4 2UYtbU0RpYHvCWcMLqovhnJqJ6IPd0sKePgqc97A/kg4/8PMaMD3i4fHCGmhv/y+MgEV j+VsBD/uBE+OXSzyCNgf+fHclM9XiLPz/p8ZQ= Received: by 10.100.74.16 with SMTP id w16mr253450ana.63.1267672786283; Wed, 03 Mar 2010 19:19:46 -0800 (PST) Received: from ?192.168.1.1? (adsl-0-94-66.jan.bellsouth.net [65.0.94.66]) by mx.google.com with ESMTPS id 16sm4386570gxk.13.2010.03.03.19.19.44 (version=SSLv3 cipher=RC4-MD5); Wed, 03 Mar 2010 19:19:45 -0800 (PST) Message-ID: <4B8F26CE.6060302@gmail.com> Date: Wed, 03 Mar 2010 21:19:42 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100223 Gentoo/2.0.2 SeaMonkey/2.0.2 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] [RFC] Remove cups from default profile to solve circular deps References: <4B8C3438.90909@gentoo.org> <1267641936.26170.5.camel@localhost> <4B8EEE42.80306@gentoo.org> <4B8F1289.8040705@gmail.com> <4B8F1389.9040609@gentoo.org> <4B8F182E.6080207@gmail.com> <4B8F19D2.1090703@gentoo.org> <4B8F1DD9.5010801@gmail.com> <4B8F23D7.9020901@gentoo.org> In-Reply-To: <4B8F23D7.9020901@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 34a8cb7c-ae2d-46d1-94e4-70c16d322f0f X-Archives-Hash: 2ff4c688679c17327e0c4427791f69a4 chrome://messenger/locale/messengercompose/composeMsgs.properties: > On 03/03/2010 09:41 PM, Dale wrote: >> So in the situation above, removing cups doesn't help any? The user >> would still have to work around the dependency problem. Is there not a >> better way to handle this? > > Agreed that there should be better ways of handling things. > > However, at the very least if somebody follows the instructions in the > Gentoo Handbook to the letter, they shouldn't end up staring at an > error message. A completely scripted install using any > non-experimental profile should "just work." > > So, removing the use flag should probably be done at least in the > interim. > > That said, I do agree that we need to try to avoid this circular > dependency in the first place. It is kind of silly that you can't > even do an emerge -u world right out of a stage3 using a fairly common > set of use flags and get a working system. > I only raised the point in case someone could come up with a better long term solution. It may be that this is the only way right now. However, it may be that someone will consider this that actually sits and writes the code for portage or decides how dependencies are calculated. Maybe a better way will present itself in the future. A good solution for most of the blocks was found so this will be dealt with at some point with a long term plan. Now watch some geek find a really simple solution next week. ;-) Dale :-) :-)