Summary: | Allow exclusions of updates to minor releases | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Shevek <gentoo> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Shevek
2003-06-11 06:10:04 UTC
I presume an implementation of this will also encourage the portage developers to increase the minor number on the 'portage' package when making a significant update, rather than just updating the release number! I would consider a solution to this bug a major benefit for systems administration. No. This would be an unsafe practice as revision changes are made when the merged package changes significantly. You would place yourself liable for security breaches and persistent/harmful bugs. This will not be considered any time soon unless there is a significant reason. 'emerge inject' provides a partial solution to your problem. Ah, OK. There was a kind of underlying assumption that when one changes a package, one also changes the version number. If this is false, then there isn't a lot we can do (except probably put paper bags on our heads). Thanks for the note. |