On Wed, 3 Dec 2014 22:53:38 +0400 Alexander V Vershilov wrote: > Let me state my idea here. > > At first I want to mention that author provided 2 different approaches to > the solution, simple dependency loop checker and another more complicated > algorithm that is a loop breaker.
No, unfortunately you get it wrong. Both earlyloopsolver and
laterloopsolver break loops and optionally warn users about found
issues. And they are not alternatives, but complements to each
other:
Early loop solvers works during dependencies cache generation, but
it can't solve issues where all dependencies in a loop are hard
("need" in terms of OpenRC). While later loop solver handles hard
dependencies at run-time.
More details are available in my another mail in this thread:
http://article.gmane.org/gmane.linux.gentoo.devel/93968
> I think that on a boot phase in case of parallel boot rc should try to
> check if loop exists and it is then print a warning and switch to a
> sequential boot.
In case of a hard loop this will fix nothing: there is no way to
determine a correct order of sequential boot in case of a all
"need" hard loop. Anyway I don't see how switch to sequential boot
may fix anything, because this doesn't solve order determination
problem at all.
Best regards,
Andrew Savchenko
pgpW61TKcEsbO.pgp
Description: PGP signature
