On 11/07/2014 09:55 PM, Jauhien Piatlicki wrote: > 07.11.14 21:44, hasufell написав(ла): >> On 11/07/2014 08:56 PM, Jauhien Piatlicki wrote: >> >> Every time people compare portage to paludis I read stuff like "but >> paludis is slower". That is incomplete information to put it diplomatic. >> >> Do you really care so much about speed that you don't mind wrong results? >> > > My original question was about Portage being too slow. And Paludis came out > just as an alternative. > > And I would like to see a detailed discussion about what's wrong from the > point of view of correctness with: > > 1. PMS > > 2. ebuilds in tree > > 3. Portage dependency solving > > Was this discussed somewhere? Could you point me there? >
The first thing that comes to my mind is dynamic dependencies. They are wrong and that has been discussed recently on this ML. If you have ever switched from portage to paludis on a full-grown system, then you know how much bad data and missing updates/blockers/dependencies are hidden. However, it seems that this issue is being addressed by the portage team, afair. Next thing that comes to my mind is: indeterministic results. I'v had LOTS of them with portage. You run an emerge, abort. You run it again... and woosh, different result. I'v not hit that case yet with paludis, unless I ran it with different configuration options.
