On Sunday 05 April 2009, Daniel Troeder wrote: > On Fri, 2009-04-03 at 13:59 -0400, Wyatt Epp wrote: > > So while gearing up for the Summer of Code, I noted a lot of things > > that I had come to accept as normal that I feel should not be so. > > Things like the danger of depclean or the way portage will only show > > one mask at a time. So I was curious...what have people that are not > > myself and my mate noticed that is mildly irritating and disruptive to > > the Gentoo experience? > > I have three ideas for improval: > > 1. > == > When updates hit the portage tree, that are known to cause problems to > lots of people - why not tell that directly after the "--sync"? > > I can remember very well the e2fsprogs-thing, where you had to download > the sources of the blocked package before uninstalling the blockers, > because wget wouldn't work without the uninstalled libs! There were LOTS > of people in forums and mailing lists asking for help. > That could have been circumvented easily, if after "--sync" a message > appeared, telling you to read /usr/portage/upgrading/12345-e2fsprogs.txt > before upgrading e2fsprogs. > The message should be displayed only, if the upgrade has not have been > done (by checking for the existence of the old packages or new package). > > 2. > == > I'd like the ebuilds to be more verbose on possible problems, runtime > dependencies, common errors and some nice hints would be great, too. > Maybe this could be switched on/off by a VARIABLE, for those who feel > annoyed. >
elog and elogv - look into it.
