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 A0E1B138C48 for ; Tue, 14 Apr 2015 02:09:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AB138E089D; Tue, 14 Apr 2015 02:09:07 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1F6DAE0854 for ; Tue, 14 Apr 2015 02:09:06 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YhqHf-0002wB-TL for gentoo-user@lists.gentoo.org; Tue, 14 Apr 2015 04:09:04 +0200 Received: from wsip-174-76-82-7.no.no.cox.net ([174.76.82.7]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Apr 2015 04:09:03 +0200 Received: from boxcars by wsip-174-76-82-7.no.no.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Apr 2015 04:09:03 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: =?UTF-8?B?wrtRwqs=?= Subject: [gentoo-user] Re: Machine completely broken; Ncursed! Date: Mon, 13 Apr 2015 21:08:56 -0500 Organization: none Message-ID: <20150413210856.03884197@sepulchrave.remarqs> References: <55292E11.9040202@verizon.net> <201504112204.26649.dilfridge@gentoo.org> <5529BF6C.7090909@verizon.net> <2227740.m4amG7ENkq@andromeda> <20150412122356.5cadb5d4@sepulchrave.remarqs> <20150412200750.355c732b@sepulchrave.remarqs> <552B58A9.6010301@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: wsip-174-76-82-7.no.no.cox.net X-Newsreader: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-pc-linux-gnu) X-Archives-Salt: 8e3c9707-7dab-4317-9b3f-e8064496d0ad X-Archives-Hash: bcd6d992b0069eba761ab0f624f5f72a On Mon, 13 Apr 2015 07:48:25 +0200 Alan McKinnon wrote: > On 13/04/2015 03:07, »Q« wrote: > > On Sun, 12 Apr 2015 21:35:07 +0300 > > Matti Nykyri wrote: > > > >>> On Apr 12, 2015, at 20:23, »Q« wrote: > >>> > >>> On Sun, 12 Apr 2015 11:12:38 +0200 > >>> "J. Roeleveld" wrote: > >>> > >>>> On Saturday, April 11, 2015 08:42:20 PM Alan Grimes wrote: > >>> > >>>>> PYTHON_TARGETS="${PYTHON_TARGETS} python2_7 python3_4" > >>>>> PYTHON_SINGLE_TARGET="python2_7" > >>>> > >>>> These are set in your profile, please do not override this. > >>>> In other words, please remove these 2 lines. > >>> > >>> I'm not the OP. (I spend less time than him on maintaining my > >>> system.) > >>> > >>> Should those variables really not be set in make.conf? I added > >>> them to make.conf some time back because portage complained about > >>> them, and if I comment them out, it complains again, like so: > > > >>> The following REQUIRED_USE flag constraints are unsatisfied: > >>> python? ( exactly-one-of ( python_single_target_python3_3 > >>> python_single_target_python3_4 python_single_target_python2_7 ) ) > > > > [snip] > > > >> This is because you have set the "python" use flag in your > >> make.conf (or package.use). > >> > >> Remove the python useflag and the problem goes away. It is not set > >> by the profile but by you. Do you really need it? > > > > I enabled it globally (in make.conf), but I think I only need it > > for one or two packages. If I remove it from USE, I get portage > > complaining about other things. > > > USE="python" is one of those flags that has no accurate meaning in > real life, and the user needs to make an informed decision. It > doesn't work like USE="sse" for example, which means packages that > can use the sse instruction set will compile for it. It's a fairly > exact meaning. > > USE="python" means "use python to do stuff" but stuff is not defined > and it's usually hard to find out what it is for a given package. For > some it means to build optional extra tools that run under python, > for some it means to create python language bindings, and for others > it could even mean some critical system function that is implemented > in python and eats your kittens if not enabled. (sort of like how > portage is implemented in python; there's no USE for it but you get > the idea). > > Usually, USE="python" should be set per-package if you need what it > does. I had it in make.conf myself in my early days and kept getting > into circular dependencies. Sorting that out took some effort. > > Portage will almost certainly complain if you take something with > far-reaching effects as USE="python" in make.conf and remove it. > > So, take each thing it is complaining about and enable or disable it > based on what you need. Tweak as necessary to get the result you want. Thanks -- that all makes sense. I'm pretty sure I have USE="python" because I thought something like "I'm going to have python, so I might as well let things use it", which I now see to be muddle-headed at best. Since it's not causing me any troubles for now, I'll wean myself off of USE="python" when there's some in which I can afford to fix whatever I break during the process.