Alec Warner wrote: >>> The tricky part then is figuring out whether something doesn't dep upon >>> c-compiler because it doesn't need one or because the ebuilds haven't >>> been updated. >>> >> I'm out of my depth here- I can't see where that would be a problem? >> > > 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?
-- gentoo-dev@gentoo.org mailing list
