And sometimes if you use --binpkg-respect-use=n and/or --with-bdeps=n you can jostle it into using more of the binaries on both passes.
Additionally, you can use the ebuild command directly to force it to just install things without checking all the dependencies, that's sometimes handy for breaking cycles too. Do pay careful attention to the merge order though. Make sure any updates to glibc happen first or else you'll wedge your system pretty badly. Having static-compiled busybox installed as a backup is often a good idea. Alternatively, fully update the system before putting in your world file, and then instead of copying in the world file all at once just run a loop to emerge the lines in it one at a time. LMP -----Original Message----- From: David Palao <pa...@csc.uni-frankfurt.de> Sent: Wednesday, May 11, 2022 5:26 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Reinstall Hi, What I would suggest is to try yo emerge @world first with a reduced list of USE flags, maybe the default, and after success you could introduce back the wanted USE flags and emerge @world once more. It could be a bit too much compilation, but if you have already binary packages, it will not be so expensive the second round, IMHO. Best On 11/5/22 11:57, Francisco Ares wrote: > Hello > > After a main HD failure, I'll have to reinstall Gentoo from almost > zero - I have a full and recent copy of the /etc directory and the > file /var/lib/portage/world in a secondary HD (along many personal > backups). > > Installation basics done, now it is time for an emerge world. > > Although the emerge lists is as huge as expected, it doesn't even > start, portage says there are cyclic USE flags that I should avoid at > the first moment, but may restore afterwards. > > But it doesn't say which are those USE flags that block each other. > > Is there any way to find those better than brute force? > > By the way, I also have a copy of all binary packages (I always use > the -b flag while emerging any package) in that second disk. But that > didn't help so far, even trying to use the -K flag. I thought on > un-tar'ing those binary packages by hand, but portage will be unaware > of this, not knowing the packages are installed. > > Any hint will be greatly appreciated! > > Thanks > > Francisco
