Bug 926088

Summary:	=sys-apps/portage-3.0.61-r1: emerge --unstable-update ...?
Product:	Portage Development	Reporter:	m1027 <m1027>
Component:	Enhancement/Feature Requests	Assignee:	Portage team <dev-portage>
Status:	UNCONFIRMED ---
Severity:	enhancement	CC:	kingjon3377
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description m1027 2024-03-03 09:34:58 UTC

Hi,

I'd be very happy to see a new option for emerge (like --unstable-update) that suggests a package update when

- the installed version is itself unstable
- and there are unstable updates available

Why:

When I install a package (here: emerge -a acme-sh), and there is an unstable version only in portage (3.0.6), I am not particular interested in this exact version. I just agree and let emerge add the keyword for *this* version (=app-crypt/acme-sh-3.0.6 ~arm64).

Also, I would not flag the package entirely with ~arm64 *without* specifying any version. Because then I'd receive unstable updates forever, even if there was a stable one in between. (Thus I would surpass future stable versions.)

The issue I have with that:

There is, e.g., acme-sh-3.0.7 now in portage. (My 3.0.6 has even been removed from portage!)

But emerge --sync && emerge -auDUN @world does not suggest an update.

How would I catch an (unstable) update for my (unstable) installed package?

Thanks