1 |
Ciaran McCreesh wrote: |
2 |
> On Sat, 16 May 2009 02:31:45 +0300 |
3 |
> Petteri Räty <betelgeuse@g.o> wrote: |
4 |
>>> On the other hand you also have to make sure you have a stable |
5 |
>>> portage for a time long enough so mostly everyone has it installed. |
6 |
>>> Otherwise you could break users systems pretty badly depending on |
7 |
>>> the packages. And Arch-Teams usually do a pretty good job in |
8 |
>>> catching such cases. |
9 |
>> How would this breakage happen? The ebuild in the vdb still has the |
10 |
>> old EAPI. |
11 |
> |
12 |
> Portage likes to use metadata from the tree version of things even if |
13 |
> there's also a version installed. This is a major nuisance, but is |
14 |
> unfortunately considered a feature. |
15 |
> |
16 |
|
17 |
I think the question here is that what Portage does when there's a newer |
18 |
EAPI in the tree version that Portage does not yet support but there's a |
19 |
supported version in the vdb. |
20 |
|
21 |
Regards, |
22 |
Petteri |