We often end up with people passing --getbinpkgonly or --usepkgonly and not realising it implies --binpkg-respect-use=n. I think it makes more sense to have these options bail by default on no matching USE for binpkgs, then we can just suggest --binpkg-respect-use=n with a warning. It's also IMO more intuitive behaviour. See also commit 3bc61292f9d44f8fd4d8655ab10e2064c70c912f Author: Gábor Oszkár Dénes <gaboroszkar@protonmail.com> Date: Thu Feb 29 21:56:00 2024 +0100 man: Document autoenabled options by --getbinpkgonly Signed-off-by: Gábor Oszkár Dénes <gaboroszkar@protonmail.com> Closes: https://github.com/gentoo/portage/pull/1291 Signed-off-by: Sam James <sam@gentoo.org>
(In reply to Sam James from comment #0) > I think it makes more sense to have these options bail by default on no > matching USE for binpkgs, then we can just suggest --binpkg-respect-use=n > with a warning. > > It's also IMO more intuitive behaviour. Completely agree, would be very nice! Thanks for CC-ing me. I think it even aligns with my comment: https://github.com/gentoo/portage/pull/1291#issuecomment-1971961752 .
I often use a command like this to check if the binhost has any package I might be interested in, regardless of the USE it is built with: > PKGDIR=/var/empty emerge -pvG --nodeps <package> We should have a better way to perform this sort of test (or somehow eliminate the need for it all together), but anyway if we default to --binpkg-respect-use=y then naturally I'll adapt to specify --binpkg-respect-use=n if appropriate.
