| 1 |
Steve Long wrote: |
| 2 |
> Alec Warner wrote: |
| 3 |
>> Er, his point being that if you don't do the upgrade all at once, you |
| 4 |
>> have two classes of package. |
| 5 |
>> |
| 6 |
>> 1. Packages that don't require C-compiler |
| 7 |
>> 2. Packages that don't yet depend upon C-compiler |
| 8 |
>> |
| 9 |
>> When doing the upgrade over a period of time the two classes of package |
| 10 |
>> become indistinguishable. Does Foo not need a C compiler, or has it |
| 11 |
>> just not gotten updated yet, it's impossible to tell without looking, so |
| 12 |
>> it's very difficult for people to report 'problem packages' because they |
| 13 |
>> have to unpack and examine the package every time (at worst). |
| 14 |
>> |
| 15 |
> I understand that there'd be two types of pkg in the tree; what I don't get |
| 16 |
> is why that is such a problem. Excuse my missing something obvious. What do |
| 17 |
> you mean by a `problem package' in this context? |
| 18 |
|
| 19 |
A problem package would be one that does not need a C compiler. It can't |
| 20 |
be distinguished from the one which was not yet changed to depend on C. |
| 21 |
|
| 22 |
The problem here is that one can not say when the whole tree is updated |
| 23 |
to the new standard, because for the packages which were not touched, it |
| 24 |
could mean that they needed no change or that they were not looked at yet. |
| 25 |
|
| 26 |
A solution to distinguish the two categories is to mark the packages |
| 27 |
which were "checked", so you know: |
| 28 |
1. If it's checked and doesn't depend on cc -> category 1 |
| 29 |
2. If it's not checked and doesn't depend on cc -> category 2 |
| 30 |
|
| 31 |
Then, when all packages are checked, the tree is upgraded. |
| 32 |
|
| 33 |
Regards, |
| 34 |
|
| 35 |
Robert |
| 36 |
-- |
| 37 |
gentoo-dev@g.o mailing list |
Archives