| 1 |
On 11/15/19 7:22 AM, Michał Górny wrote: |
| 2 |
> |
| 3 |
> https://devmanual.gentoo.org/general-concepts/ebuild-revisions/index.html |
| 4 |
> |
| 5 |
|
| 6 |
Two things on that page are outright wrong: |
| 7 |
|
| 8 |
1. If the package has stable keywords, they should be moved to the new |
| 9 |
revision without dropping. To commit the ebuild, repoman commit |
| 10 |
--straight-to-stable option should be used. |
| 11 |
|
| 12 |
That violates our other stabilization policies and common sense. |
| 13 |
|
| 14 |
2. Examples of changes that can be done without a revision bump are... |
| 15 |
|
| 16 |
adding a new USE flag or removing an existing one (since change in |
| 17 |
USE flags is going to trigger --changed-use rebuild), |
| 18 |
|
| 19 |
The --changed-use flag is not default, not part of the PMS, and slows |
| 20 |
portage down even more than it already is. The council ratified the PMS |
| 21 |
and the associated GLEP, and following this advice breaks PMS-compliant |
| 22 |
package managers. |
Archives