64470 – 'emerge important flag' feature request

Bug 64470 - 'emerge important flag' feature request

Summary: 'emerge important flag' feature request

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Conceptual/Abstract Ideas (show other bugs)
Hardware:	All All

Importance:	High enhancement (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Duplicates (1):	72830 (view as bug list)
Depends on:
Blocks:

Reported:	2004-09-17 18:11 UTC by Daniel Webert
Modified:	2004-12-05 10:33 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Daniel Webert 2004-09-17 18:11:59 UTC

'emerge important flag' feature request

<snip>
[ebuild     U ] net-print/cups-1.1.21 [1.1.21_rc2] -debug +pam -slp +ssl 0 kB
</snip>

- emerge tells my to update cups-1.1.21 - cups 1.1.21_rc2 was kicked out of the cvs
- can we make a marker or flag-something in the emerge-output, that tells me - this update is "important", because the old-installed version (rc2) does no longer exist in portage? 
- this could be also usefull for security-related-updates (example: i have openssh-3.8p installed - it has sec-bug, gets kicked out of cvs, and 3.9p gets in - not everybody reads the glsa ...)

Comment 1 SpanKY gentoo-dev

2004-09-19 14:58:29 UTC

`emerge security` handles the GLSA stuff

as for the rest, i dont see any need for it ... read the ChangeLog for updated info ...

Comment 2 Daniel Webert 2004-12-05 10:33:26 UTC

*** Bug 72830 has been marked as a duplicate of this bug. ***