|
Lines 17-22
Ebuilds should have their <c>-rX</c> incremented whenever a change is made which
Link Here
|
| 17 |
will make a substantial difference to what gets installed by the package <d/> by |
17 |
will make a substantial difference to what gets installed by the package <d/> by |
| 18 |
substantial, we generally mean "something for which many users would want to |
18 |
substantial, we generally mean "something for which many users would want to |
| 19 |
upgrade". This is usually for bugfixes. |
19 |
upgrade". This is usually for bugfixes. |
|
|
20 |
Revision bumps are also necessary whenever runtime dependencies change, because |
| 21 |
that is the only reliable way to update the users VDB and ensure it is in a |
| 22 |
consistent state. |
| 20 |
For any such revision bump, the new ebuild should be based on the |
23 |
For any such revision bump, the new ebuild should be based on the |
| 21 |
previous revision to ensure that fixes aren't dropped accidentally. |
24 |
previous revision to ensure that fixes aren't dropped accidentally. |
| 22 |
</p> |
25 |
</p> |
| 23 |
- |
|
|
