Re: [gentoo-user] Re: Machine completely broken; Ncursed!

[Alec Ten Harmsel <alec@alectenharmsel.com>]

On 04/12/2015 09:38 PM, »Q« wrote:
> On Sun, 12 Apr 2015 21:24:48 -0400
> Alec Ten Harmsel <alec@alectenharmsel.com> 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.

You can find all the defaults here:
/usr/portage/profiles/base/make.defaults. I don't think the KDE profile
overrides any of the python/ruby stuff, just USE. It's strange that you
are getting that error from util-linux; I would recommend getting rid of
the USE_PYTHON="2.7" line from make.conf and, personally, avoid having
so many USE flags in make.conf.

Alec