| 1 |
On Sun, 12 Apr 2015 20:38:17 -0500, »Q« wrote: |
| 2 |
|
| 3 |
> > It's not a bad idea to manage the PYTHON_TARGETS, |
| 4 |
> > PYTHON_SINGLE_TARGET, and RUBY_TARGET variables if you *need* a |
| 5 |
> > specific version of python or ruby. If you do not, I would say it is |
| 6 |
> > bad. These are set in the profile so that the maintainers can decide |
| 7 |
> > when to update to a new stable version. Since all of the various |
| 8 |
> > python and ruby libraries are installed from source, it's generally a |
| 9 |
> > good idea to wait for the maintainers to stabilize a certain version |
| 10 |
> > since that means the library support is also good. |
| 11 |
> |
| 12 |
> How can I find out whether the profile is setting those variables? |
| 13 |
|
| 14 |
By removing USE="-*". At the moment it doesn't matter which profile you |
| 15 |
use or what it sets as you are then telling portage to ignore all its |
| 16 |
settings, even the critical ones. As portage evolves and the devs update |
| 17 |
the profiles to keep in line, your system will be come gradually more |
| 18 |
broken, as happened when PYTHON_TARGET variables were introduced. |
| 19 |
|
| 20 |
|
| 21 |
-- |
| 22 |
Neil Bothwick |
| 23 |
|
| 24 |
The modem is the message. |
Archives