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 5D624138C48 for ; Mon, 13 Apr 2015 01:38:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ACA0CE09DD; Mon, 13 Apr 2015 01:38:27 +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 509BCE09B1 for ; Mon, 13 Apr 2015 01:38:26 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YhTKR-0004wT-QL for gentoo-user@lists.gentoo.org; Mon, 13 Apr 2015 03:38:23 +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 ; Mon, 13 Apr 2015 03:38:23 +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 ; Mon, 13 Apr 2015 03:38:23 +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: Sun, 12 Apr 2015 20:38:17 -0500 Organization: none Message-ID: <20150412203817.0cd1775e@sepulchrave.remarqs> References: <55292E11.9040202@verizon.net> <2227740.m4amG7ENkq@andromeda> <20150412122356.5cadb5d4@sepulchrave.remarqs> <1548532.LqqDBuMcQi@andromeda> <20150412201552.3e0aca16@sepulchrave.remarqs> <552B1AE0.5030507@alectenharmsel.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: bcdf388f-78d4-4546-9aff-43e0942524c1 X-Archives-Hash: 97cf175397ac59eaeba2ff6c331ec9be On Sun, 12 Apr 2015 21:24:48 -0400 Alec Ten Harmsel wrote: > On 04/12/2015 09:15 PM, »Q« wrote: > > > > Before you pore through it, I guess I should point out that it's not > > causing me any problems -- I was just curious about why it would be > > a bad idea for me to manage those PYTHON_* variables myself. I > > guess the most notable thing about my make.conf is that I'm one of > > those crazy USE="-*" people. > > It's not a bad idea to manage the PYTHON_TARGETS, > PYTHON_SINGLE_TARGET, and RUBY_TARGET variables if you *need* a > specific version of python or ruby. If you do not, I would say it is > bad. These are set in the profile so that the maintainers can decide > when to update to a new stable version. Since all of the various > python and ruby libraries are installed from source, it's generally a > good idea to wait for the maintainers to stabilize a certain version > since that means the library support is also good. How can I find out whether the profile is setting those variables? ISTM the emerge errors I posted earlier, which happen if I get rid of those variables in make.conf, indicate that they are not being set at all. When a new version of python (or ruby, I guess) is stabilized, I do have to spend some time making sure those variables are sanely set, and I'd rather just leave it up to the devs. > Also, using the KDE profile and having USE="-*" seem contrary. One of > the main reasons to use a profile is to get a relevant set of USE > flags. I don't want the profile's USE flags, but I still thought it best to select the profile that matches what I use the machine for.