| 1 |
On 11/23/2010 09:32 AM, Mike Frysinger wrote: |
| 2 |
> On Tuesday, November 23, 2010 01:36:15 Graham Murray wrote: |
| 3 |
>> Mike Frysinger<vapier@g.o> writes: |
| 4 |
>>> well, not quite. the way we agreed in the past was to not revbump the |
| 5 |
>>> masked package, but once it was unmasked, we revbump it just once at |
| 6 |
>>> that point. |
| 7 |
>> |
| 8 |
>> Is there somewhere which tells users when there are upgrades to |
| 9 |
>> toolchain packages which are not revbumped once they have been unmasked |
| 10 |
>> and in ~arch? |
| 11 |
> |
| 12 |
> if they arent revbumped, then the changes dont matter to you |
| 13 |
|
| 14 |
This isn't always the case though, due to developer mistakes. Sometimes |
| 15 |
when doing emerge -e system, there are changes in /etc files that affect |
| 16 |
runtime behavior rather than build behavior. And it seems to happen |
| 17 |
quite often. This is with non-masked packages though. |
| 18 |
|
| 19 |
It's the reason I do emerge -e system quite often (every 3 months or |
| 20 |
so); runtime fixes are applied by devs without revbumps. |
Archives