On 19/09/2021 14:06, Philip Webb wrote:
210919 antlists wrote:
On 19/09/2021 08:03, Philip Webb wrote:
Portage ought to be able to recognise when a set of pkgs
are creating destructive circular dependencies among themselves
& resolve the conflict by updating all of them together.
Until you hit my version of the problem,
where if a is not there, b crashes when you try to build it ...
And of course, installing a crashes because b is not there ...
So you emerge both together :
I've never run into a version of your case where that wasn't the solution.
And I don't expect anything like that to happen
with a related group of pkgs like Qt or KDE.
Well, seeing the fact that this particular case is plastered all over
the net with people trying to solve it, then emerging the two together
DOESN'T solve it.
The problem is that - in order to emerge either one - THE OTHER ONE MUST
HAVE BEEN EMERGED FIRST. Whoops ...
(If they're not already on your system, try installing something that
requires truetype. That will call in freetype, which won't emerge
because harfbuzz isn't there. But harfbuzz won't emerge, because
freetype isn't there. As in, they won't emerge even if you try and force
it, because configure will crash because it can't find the other one.)
Cheers,
Wol
