1 |
On 03/18/2010 10:10 PM, Ciaran McCreesh wrote: |
2 |
> On Thu, 18 Mar 2010 22:02:38 +0200 |
3 |
> Petteri Räty <betelgeuse@g.o> wrote: |
4 |
>> Here's how we could change Portage behavior for pulling new slots that |
5 |
>> are not strictly required: |
6 |
>> |
7 |
>> - for packages in the world file install as soon as available |
8 |
>> |
9 |
>> - for dependencies install the new slot if everything works with the |
10 |
>> new slot |
11 |
>> |
12 |
>> This would mean that Portage would stay with 2.6 as long as you have |
13 |
>> something that doesn't work with 3.x installed. |
14 |
> |
15 |
> Why would you want the majority of your packages that can use a newer, |
16 |
> shinier version of a library to continue using the old version? Do you |
17 |
> really want to stick with Qt3 until every single app you have supports |
18 |
> Qt4? |
19 |
> |
20 |
|
21 |
PM can make it configurable. It's a trade off between having as few |
22 |
packages as possible installed and upgrading as soon as possible. In |
23 |
general I want to keep my installed stuff to minimum. I don't have a |
24 |
need for new stuff that I don't know exists. If I know packages can make |
25 |
use of it to give me something new and shiny I can always manually |
26 |
request the new slot to be installed. Most likely before everything is |
27 |
ported over there is something written to require the new version |
28 |
explicitly so it's sooner than you are saying. |
29 |
|
30 |
Regards, |
31 |
Petteri |