On Thu, Jan 20, 2022 at 4:10 PM Piotr Karbowski <slashbe...@gentoo.org> wrote: > > Ideally we'd have some way to mark binary packages with new EAPI and > have FEATURES flag like 'prefer-binary' and go with -bin in case there's > || ( ) dependencies list, regardless of the original order in virtual. > This way everyone could be happy and not choose one workflow over another.
Ideally we'd just have a repository of binary builds for everything with default USE flags for a few profiles, and users could choose to configure portage to just download the binary package if the flags match, and of course this could be overridden per-package. Then there would be no need for -bin anything. We have to maintain half of that for the stage builds anyway. I don't have a strong preference but I doubt that many of our users receive any benefit whatsoever from building rust from source, and so I'd suggest -bin ought to be the default. However, having a pre-installation notice that the -bin is available with a link/etc to how to use it seems reasonable. I bet a lot of users spend more time getting the source build to work than it would take to just reconfigure things so that they get the -bin. If users are building in a tmpfs or with numerous parallel jobs odds are that they'll end up with a build failure for rust - CPU cores are way cheaper than RAM. -- Rich
