| 1 |
On 03/18/2010 10:21 PM, Thomas Sachau wrote: |
| 2 |
> On 03/18/2010 09:02 PM, Petteri Räty wrote: |
| 3 |
>> On 03/18/2010 09:43 PM, Thomas Sachau wrote: |
| 4 |
>>> |
| 5 |
>>> So my vote goes for changing the dependency strings for affected packages. |
| 6 |
>>> |
| 7 |
>> |
| 8 |
>> Here's some thoughts on the matter: |
| 9 |
>> |
| 10 |
>> - dev-lang/python is correct if the package works with all python |
| 11 |
>> versions in tree |
| 12 |
>> |
| 13 |
>> - in general we want new slots of packages like gcc being pulled in |
| 14 |
>> |
| 15 |
>> Here's how we could change Portage behavior for pulling new slots that |
| 16 |
>> are not strictly required: |
| 17 |
>> |
| 18 |
>> - for packages in the world file install as soon as available |
| 19 |
>> |
| 20 |
>> - for dependencies install the new slot if everything works with the new |
| 21 |
>> slot |
| 22 |
>> |
| 23 |
>> This would mean that Portage would stay with 2.6 as long as you have |
| 24 |
>> something that doesn't work with 3.x installed. |
| 25 |
>> |
| 26 |
>> Regards, |
| 27 |
>> Petteri |
| 28 |
>> |
| 29 |
> |
| 30 |
> How do you detect this? |
| 31 |
|
| 32 |
By looking at the dependency graph? |
| 33 |
|
| 34 |
> Also, what about a new slot for python-2? E.g. 2.7? |
| 35 |
|
| 36 |
Handled by the same rules. |
| 37 |
|
| 38 |
> And do you want to add a special rule to portage just for the special case of python instead of the |
| 39 |
> ebuilds/eclasses having the issue? |
| 40 |
> |
| 41 |
|
| 42 |
What issue is there with ebuilds/eclasses? Both should reflect the deps |
| 43 |
as well as can be done with current EAPIs. If they don't, they need to |
| 44 |
be fixed. |
| 45 |
|
| 46 |
Regards, |
| 47 |
Petteri |
Archives