Summary: | The emerge messages should take into account the previous version of the ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | poletti.marco |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED CANTFIX | ||
Severity: | enhancement | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
poletti.marco
2012-10-29 21:55:04 UTC
This isn't a single issue. If you could figure out which ebuilds show these irrelevant messages, you could file separate bug reports for each of them and then make them block this bug, which we could then turn into a "tracker" bug. Until then, this bug cannot be fixed or even addressed. Is it possible to fix the issue just by modifying those ebuilds? I thought that a portage modification was required (but I don't really know). I.e.: can an ebuild know if it's a new install or an update? If it's an update, does it know which is the currently-installed version? Apparently it's possible to get that information by checking the value of REPLACING_VERSIONS. I have opened a tracker bug: Bug 440214. |