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 4C510138C48 for ; Tue, 14 Apr 2015 03:52:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9B710E0903; Tue, 14 Apr 2015 03:52:13 +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 4DA7EE08F7 for ; Tue, 14 Apr 2015 03:52:12 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YhrtQ-0006GI-VT for gentoo-user@lists.gentoo.org; Tue, 14 Apr 2015 05:52:09 +0200 Received: from wsip-72-205-174-150.no.no.cox.net ([72.205.174.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Apr 2015 05:52:08 +0200 Received: from boxcars by wsip-72-205-174-150.no.no.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Apr 2015 05:52:08 +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 22:51:58 -0500 Organization: none Message-ID: <20150413225158.48b9c0f9@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> <20150412203817.0cd1775e@sepulchrave.remarqs> <20150413085157.293dfb87@digimed.co.uk> 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-72-205-174-150.no.no.cox.net X-Newsreader: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-pc-linux-gnu) X-Archives-Salt: 105234df-7a50-4d08-82cc-55a4a4a1c5c4 X-Archives-Hash: 3281702b275163299a9e36d949638890 On Mon, 13 Apr 2015 08:51:57 +0100 Neil Bothwick wrote: > On Sun, 12 Apr 2015 20:38:17 -0500, »Q« wrote: > > > > 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? > > By removing USE="-*". At the moment it doesn't matter which profile > you use or what it sets as you are then telling portage to ignore all > its settings, even the critical ones. I'm getting conflicting info on this. Do profiles really only set USE flags or do they do something else as well? (Or does USE="-*" affect things *other* than USE?) > As portage evolves and the devs update the profiles to keep in line, > your system will be come gradually more broken, as happened when > PYTHON_TARGET variables were introduced. Following this list and -dev seems to keep me up-to-date on the changes, as happened when the PYTHON_ variables were introduced. AFAICS, the only brokenness so far is that I'm complicating my life more than several people here think I should be.