When emerging @world after sync sometimes a binpkg is just no yet readily available on servers, but would be after some hours at the next day. For larger packages I manually look up on the server whether a binpkg is principally provided so I can guess that it will arrive in the future and then prolong the emerge. For convenience reasons I then prolong the entire `emerge @world`, but it would be great if portage could do that automatically per package. That is, I propose an option like `emerge --wait-for-binpkg` that can (1) determine if for a package and the given use flag a binpkg is going to be provided (2) and if it is not available yet then emerging is skipped. Without this option there is always a certain window (worst-case a day?) between (i) the arrival of a new ebuild in portage and (ii) the availability of the binpkg, in which all users are building the package where otherwise a binpkg would have been available after point (ii). However, I imagine that this feature is not so trivial to implement: Step (1) I do manually based on a heuristic: If for sys-devel/gcc binary packages are provided I guess that for the given version it is only a matter of time until it will be provided and after that it can be checked it is provided for the given use-flag set. However, it would be good to know as a fact that a binpkg for a given package and use-flag set is going to be provided. But this predicate would be interesting independently of this feature request, I think. Step (2), of course, needs to be evaluated transitively on the dependency graph of packages. That is, if a package is skipped so need all packages be skipped that can reach the former on the dependency graph. But this – I guess – must already be part of the current dependency resolution. There has been a discussion on #gentoo@libera.irc on 2024-01-23 (around 14:00 to 18:00 CET), and I was asked to file this bug. Reproducible: Always
