| 1 |
On 03/18/2010 09:43 PM, Thomas Sachau wrote: |
| 2 |
> |
| 3 |
> So my vote goes for changing the dependency strings for affected packages. |
| 4 |
> |
| 5 |
|
| 6 |
Here's some thoughts on the matter: |
| 7 |
|
| 8 |
- dev-lang/python is correct if the package works with all python |
| 9 |
versions in tree |
| 10 |
|
| 11 |
- in general we want new slots of packages like gcc being pulled in |
| 12 |
|
| 13 |
Here's how we could change Portage behavior for pulling new slots that |
| 14 |
are not strictly required: |
| 15 |
|
| 16 |
- for packages in the world file install as soon as available |
| 17 |
|
| 18 |
- for dependencies install the new slot if everything works with the new |
| 19 |
slot |
| 20 |
|
| 21 |
This would mean that Portage would stay with 2.6 as long as you have |
| 22 |
something that doesn't work with 3.x installed. |
| 23 |
|
| 24 |
Regards, |
| 25 |
Petteri |
Archives