On 7/15/24 5:54 AM, J. Aho wrote: > The main issue is that you aren't syncing portage towards the bin > server, which makes things out of sync and those you will be building a > lot of the packages instead of fetching the binary files when they are > built.
As noted earlier, it's more complicated than that. Portage can handle the case you describe just fine, in the sense that you will be building a lot of the packages instead of fetching the binary files. In which case, you don't need to set FEATURES="-getbinpkg" on a per package basis, since they will simply be built from source anyway. The problem comes when portage says there *is* a binary package available, because the index of packages says there is one, then it tries to download the binary file itself and receives a 404 error. That causes portage to crash since it doesn't expect the 404. > If they didn't, then I had the issue as you describe and I had > discussion about this on the gentoo irc channels, but as back then few > people used binhosts so they didn't understand the issue and those > portage don't support to do what you want to do, to filter out new > ebuilds that don't have a binary package at the binhost, just wait > another 20 years and then maybe. I understand where you are coming from :) because I refused to become a Gentoo user until there were official binhosts. There is as of 2024 a tracking issue for the bug you described, and with that public record of what to improve, some progress has been made to get it to work. I expect it to take significantly less than 20 years to deploy: the current version of portage stabilized for amd64 causes a binhost to expose the git commit for gentoo.git that it was built for, and the plan is that you should be able to have `emerge --sync` just sync to that revision as announced by the binhost. I will admit that it took us 5 months from time of reporting until portage made the progress it has so far, but I'm inclined to blame that on FOSS software being FOSS and people having other things to do with their time. Hopefully we'll only need to wait another couple of months for it to be full solved. :) Please do consider watching https://bugs.gentoo.org/924772 for further progress. -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
