Steve Long wrote: > Alec Warner wrote: >> Er, his point being that if you don't do the upgrade all at once, you >> have two classes of package. >> >> 1. Packages that don't require C-compiler >> 2. Packages that don't yet depend upon C-compiler >> >> When doing the upgrade over a period of time the two classes of package >> become indistinguishable. Does Foo not need a C compiler, or has it >> just not gotten updated yet, it's impossible to tell without looking, so >> it's very difficult for people to report 'problem packages' because they >> have to unpack and examine the package every time (at worst). >> > I understand that there'd be two types of pkg in the tree; what I don't get > is why that is such a problem. Excuse my missing something obvious. What do > you mean by a `problem package' in this context?
A problem package would be one that does not need a C compiler. It can't be distinguished from the one which was not yet changed to depend on C. The problem here is that one can not say when the whole tree is updated to the new standard, because for the packages which were not touched, it could mean that they needed no change or that they were not looked at yet. A solution to distinguish the two categories is to mark the packages which were "checked", so you know: 1. If it's checked and doesn't depend on cc -> category 1 2. If it's not checked and doesn't depend on cc -> category 2 Then, when all packages are checked, the tree is upgraded. Regards, Robert -- gentoo-dev@gentoo.org mailing list
