Hello Heroxbd, Friday, January 10, 2014, 4:16:47 AM, you wrote:
>> The ebuilds have approximately the same time to install, the failure >> rate is about the same, emerge is getting slower. > I am curious about the slowness of emerge. > How about profile the portage and rewrite the time-crucial part in > C/C++, or ideally, borrowing the counterpart from paludis? How feasible > is that? > I guess the dep-tree calculation is the slowest part. If you had the PortageQOS you would see what change slowed down Portage. And the problem could have already been fixed. You could make fast and correct decisions. True, it could be possible that some parts of the portage need to be rewritten. May be Python was the wrong decision, may be it's better to use C++. (Yes, I expect to be condemned over here before I'm banned, a sacrifice for the better Gentoo somebody had to make). Do you remember how many problems portage had with Python? It's like Gentoo is for Python not for anything else. Why not to get rid of Python at all. What is so great in Python that Gentoo exists for the sake of it? And when next thing is introduced - you can see how it works world wide. On some older PC the new portage works for 4-6 minutes before it FAILS. If the portage is going to be a little bit smarter again - you would need a new hardware to run it. And nobody cares, of course it's better to hide don't know or run from problems than know about them and fix them. 300 devs, are NOT ABLE to make portage fast in 8 years. -- Best regards, Igor mailto:lanthrus...@gmail.com
