this looks fine: $ emerge -pq --nodeps laskdjfasdf emerge: there are no ebuilds to satisfy "laskdjfasdf". and this is fine: $ emerge -pq --nodeps nano [ebuild R ] app-editors/nano-2.5.0 USE="magic ncurses nls spell unicode -debug -justify -minimal -slang -static" but this is misleading: $ emerge -pq --nodeps nano -K emerge: there are no ebuilds to satisfy "nano". it should say "binary packages" instead of "ebuilds", and probably make a better suggestion
I can look into changing the message when usepkgonly is active. But what do you mean by "make a better suggestion"?
Patch posted for review here: https://archives.gentoo.org/gentoo-portage-dev/message/17a4ec233f16a520e30c8cef65c1b640
(In reply to Alexander Berntsen from comment #1) if the info is readily available, it could mention whether there's an ebuild available (to build from source) or it's a completely unknown package
(In reply to SpanKY from comment #3) > (In reply to Alexander Berntsen from comment #1) > > if the info is readily available, it could mention whether there's an ebuild > available (to build from source) or it's a completely unknown package I'll add a different bug for that.
Patch is now in git: https://gitweb.gentoo.org/proj/portage.git/commit/?id=9c9165fb9420a285e8e2c62cb9ba8eb91120cb66 (I keep forgetting that hitting return when selecting a keyword makes bugzilla send the entire form...)
Fixed in 2.2.28. Commit hash changed: https://gitweb.gentoo.org/proj/portage.git/commit/?id=8c9b1d6a7c115344cdc5bd8e7d122ab721aeb53a