1 |
On Sun, 12 Apr 2015 21:24:48 -0400 |
2 |
Alec Ten Harmsel <alec@××××××××××××××.com> wrote: |
3 |
|
4 |
> On 04/12/2015 09:15 PM, »Q« wrote: |
5 |
> > |
6 |
> > Before you pore through it, I guess I should point out that it's not |
7 |
> > causing me any problems -- I was just curious about why it would be |
8 |
> > a bad idea for me to manage those PYTHON_* variables myself. I |
9 |
> > guess the most notable thing about my make.conf is that I'm one of |
10 |
> > those crazy USE="-*" people. |
11 |
> |
12 |
> It's not a bad idea to manage the PYTHON_TARGETS, |
13 |
> PYTHON_SINGLE_TARGET, and RUBY_TARGET variables if you *need* a |
14 |
> specific version of python or ruby. If you do not, I would say it is |
15 |
> bad. These are set in the profile so that the maintainers can decide |
16 |
> when to update to a new stable version. Since all of the various |
17 |
> python and ruby libraries are installed from source, it's generally a |
18 |
> good idea to wait for the maintainers to stabilize a certain version |
19 |
> since that means the library support is also good. |
20 |
|
21 |
How can I find out whether the profile is setting those variables? |
22 |
ISTM the emerge errors I posted earlier, which happen if I get rid of |
23 |
those variables in make.conf, indicate that they are not being set at |
24 |
all. |
25 |
|
26 |
When a new version of python (or ruby, I guess) is stabilized, I do |
27 |
have to spend some time making sure those variables are sanely set, and |
28 |
I'd rather just leave it up to the devs. |
29 |
|
30 |
> Also, using the KDE profile and having USE="-*" seem contrary. One of |
31 |
> the main reasons to use a profile is to get a relevant set of USE |
32 |
> flags. |
33 |
|
34 |
I don't want the profile's USE flags, but I still thought it best to |
35 |
select the profile that matches what I use the machine for. |