Summary: | seporate gentoo specific config options into own ebuild r1 r2 r3 recompile too much | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Aaron Peterson <alpeterson> |
Component: | Enhancement/Feature Requests | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | dberkholz |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aaron Peterson
2005-01-14 18:53:57 UTC
Care to share which xorg you're talking about? Well, my understanding of the policy is that these kinds of changes do not warrant new revisions. The actual judgement is not that easy, and also depends on the size of the package, and the impact of the change. In any case most revisions are not really necessary for operation. To take that into account does however involve some manual revision of the updates to be performed. I agree that a tool that would allow you to "bump" revisions (like inject used to be useable for) would be helpful for this (you can do it manually). In the end however it might be better to only do updates on security issues (take a look at glsa-check) and improvements to packages you care for. That way you don't get all those recompiles at the cost of not being super-current. This is not a portage bug or feature request from what I can tell. x11 herd, please handle this. In xorg's specific case, I'm rather confident that your thought is not correct on just config file changes in an update. In the more general case, you'll be better off posting to gentoo-dev rather than filing a bug, so I suggest you do that. |