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 <gentoo-dev+bounces-39778-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1NnNfy-0004s3-70
	for garchives@archives.gentoo.org; Fri, 05 Mar 2010 02:54:09 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 05E18E0C5E;
	Fri,  5 Mar 2010 02:54:03 +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 F1C0FE0AC4
	for <gentoo-dev@lists.gentoo.org>; Fri,  5 Mar 2010 02:53:51 +0000 (UTC)
Received: by gyg4 with SMTP id 4so1426402gyg.40
        for <gentoo-dev@lists.gentoo.org>; Thu, 04 Mar 2010 18:53:51 -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=Y00KN6P/aT2V6T2IhiGiyRhlOiOUFqTkhhuhH1OeSbI=;
        b=UkGXszMzY2a13H0TdURGYcYJYnGrUexE0jXIyFz0jP14YrUVqJI77ToeGZzt03f1nm
         gBotCq8NIa/xlmzhQVeshjcG49tKhtgj6ZspNBE0UE6SnRKA6ZvqZhsiSv+sJUVdT0v8
         ecLP0o5bYbQVr57aoZ6Iwg1gAMBiZ3wu2voj4=
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=caVimNxf7ad9dU+6rbhIDMXuuAlZtZ3eyR8KMY6qXI+nvSMCBmMWkvYM9fzYNL7FTJ
         AdMHSqiv/t8Bavgm1j353CgM/GCPM2SWOoOSM3YWuqXmH6lsGX+uZuE22LK5pPRTcXFM
         r3i/THHk3/X/yFbKvxxzqlEKIz/Tma/sLCXW4=
Received: by 10.100.235.36 with SMTP id i36mr910776anh.104.1267757631547;
        Thu, 04 Mar 2010 18:53:51 -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 15sm478067gxk.14.2010.03.04.18.53.49
        (version=SSLv3 cipher=RC4-MD5);
        Thu, 04 Mar 2010 18:53:50 -0800 (PST)
Message-ID: <4B90723B.8040904@gmail.com>
Date: Thu, 04 Mar 2010 20:53:47 -0600
From: Dale <rdalek1967@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100304 Gentoo/2.0.3 SeaMonkey/2.0.3
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
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: <e117dbb91003011324j1d3df0cfndc74d1e711b71fae@mail.gmail.com> <e117dbb91003041539y27e27bbq6e5b2d197b49b586@mail.gmail.com> <4B9049A3.5020805@gmail.com> <201003050957.22890.mail@patrick-nagel.net>
In-Reply-To: <201003050957.22890.mail@patrick-nagel.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Archives-Salt: 554dee04-a313-4a7c-b505-1564455bdbaa
X-Archives-Hash: 333e4c2d44eb85ba76b9c9c6b58f0265

chrome://messenger/locale/messengercompose/composeMsgs.properties:
> Hi,
>
> On 2010-03-05 00:00 UTC Dale wrote:
>    
>> chrome://messenger/locale/messengercompose/composeMsgs.properties:
>>      
>>> On 5 March 2010 00:27, Dale<rdalek1967@gmail.com>   wrote:
>>>        
>>>>>>> But this issue can be discussed separately from whether cups
>>>>>>> should be enabled in profiles.
>>>>>>>                
>>>> Actually, it is the problem.  You want to remove cups to solve the
>>>> problem of circular dependencies.
>>>>          
>>> What I wrote was:
>>>        
>>>>> What it fixes is (1) the circular dependency that people run into on a
>>>>> fresh install and the default desktop profile, and (2) the default
>>>>> dependency on cups that many users do not need.
>>>>>            
>>> But if you choose to ignore what I actually write, then I'd better stop
>>> responding.
>>>
>>> Good night,
>>>        
>> You notice what I wrote?  If I had to install Gentoo again, I would copy
>> or set my USE flags first then install.  If I do that right after
>> unpacking the tarball, which is how it should be done, then you have
>> fixed nothing.  The problem you claim to have fixed is not fixed at all.
>>
>> Maybe it is not me that should stop responding?
>>      
> Obviously, users who "re-install" Gentoo the way you do will have less
> difficulties resolving a circular dependency than those who are just following
> the guide and getting their first Gentoo experience.
>
> Patrick.
>
>    

Not quite.  If a person reads the docs and other howto's, they will know 
to set up the USE flags and other things in make.conf.  Isn't the USE 
flags one of Gentoo's strong points?  It is one reason I chose Gentoo 
after all.  I have read where others say it as a strong point as well.  
So, the same thing will most likely happen to anyone installing Gentoo.

Case in point, I also went here:

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6

If you scroll down to section 2.3, that is where it tells you to select 
your profile.  Want to guess what is next?  Yep, setting the USE flags.  
So, chroot in, sync the tree, select the profile then add your USE 
flags.  So far, we are where we was several replies ago.  Same problem 
and that is following the official install guide.  I wasn't looking at 
the expert guide, that is the general user guide for newbies.

If this was some rarely used flag then maybe this would make a little 
sense.  This is cups.  It's not something that is rarely used or that 
someone even a little familiar with Linux wouldn't know to turn it on.  
They may not know what cups stands for but they know it makes their 
printer work.

I guess like with some other things, the devs can do it their way and 
let that be the end of it.  I just feel the best way is to find a long 
term fix for this and other similar issues.  If it is not done now, it 
will just pile up until it is fixed.  Just like the problem with 
blocks.  It got bad enough that someone had to find a way to fix it.  
Someone did just that.  I don't know who that person is but that was a 
job well done.  We need the same type of person to deal with this.

Dale

:-)  :-)