On 28/10/2017 22:39, Anthony Youngman wrote: > On 28/10/17 20:54, Alan McKinnon wrote: >> Portage cannot do that, it is backed by silicon and has no concept of >> meaning. So it has only one real choice - it can do it all or it does >> not try. >> >> I'm not surprised Zac never tried implementing partial graph resolution >> for the very simple reason that if you try do it, you have no idea what >> is going to be built. That is the opposite of what portage must deliver. > > Why is it the opposite of what portage *must* deliver? All I'm asking is > that portage build *what it can*. In other words, I know EXACTLY what it > is going to deliver - its best effort!
Dude, calm down. Showing me that you are upset isn't going to change jack shit. > > And why does portage *have* to choose between all or nothing? All I'm > asking is that if it can't resolve everything, I want it to resolve > everything it can. Silicon is perfectly capable of making that decision. because "everything it can" is not necessarily the same thing as "everything it should" or "everything it was asked to do" Portage has no idea at all why the depgraph failed to resolve fully at the start. It knows about blockers that are in it's own ebuilds and can deal with those; the way ebuilds are spec'ed a package manager can cleave off an entire branch of the tree and build the remainder fully confident that each part of what it then does build is identical to the same parts if the blockers never hit the rest. It's deterministic and so portage can continue. For everything else, the input is not completely known therefore the output cannot be completely known either and portage does the correct thing and not try guess. This is a good thing. > > If I say "emerge -u world" I have no idea what it's going to build, if I > say "emerge -u best-efforts", I have no idea what it's going to build, > where's the difference? > > What I do know, is if I repeat "emerge -u best-efforts" several times, I > will end up (in all likelihood) with the same result as "emerge -u world". No, you will not. In this case, what portage will give is not the sum of it's individual parts as there is a real risk that some attributes of the various parts are WRONG. Therefore the output can be WRONG. It really is that simple. You even said it yourself when you used the phrase "in all likelihood". What about when it isn't? This is a package manager and package managers have one singular objective that the code must always deliver: the output must be entirely deterministic. Anything other than that and you do not have a package manager anymore, now you have software that puts stuff on a disk. Portage is doing the right thing when it detects invalid input that it cannot reliably - it stops. But feel free to disagree. If you can do this, the proof is in code and patches. Got any? -- Alan McKinnon alan.mckin...@gmail.com
