| 1 |
On 21/07/14 22:37, hasufell wrote: |
| 2 |
> afaiu dynamic deps are broken and not defined in PMS |
| 3 |
> |
| 4 |
> still... people seem to fix deps without revbumping, causing users who |
| 5 |
> either don't use dynamic deps (it's optional for portage through |
| 6 |
> --dynamic-deps=y, although it's on by default) or who use a different PM |
| 7 |
> to not get the fix, at worst resulting in broken dependency calculation |
| 8 |
> |
| 9 |
> suggestion: |
| 10 |
> * stop fixing dependencies without revbumping |
| 11 |
> * add an appropriate question to the dev quiz |
| 12 |
> * remove dynamic deps from portage (afair that is already considered by |
| 13 |
> the portage team) |
| 14 |
> |
| 15 |
|
| 16 |
Revision bumping for dependency change that doesn't cause the package's |
| 17 |
file content |
| 18 |
to change doesn't make sense; triggers useless rebuilds for users. |
| 19 |
|
| 20 |
Portage is the official package manager, and has dynamic deps enabled by |
| 21 |
default. |
| 22 |
|
| 23 |
And it's already in ebuild-quiz.txt to ensure knowing when to, or not to, |
| 24 |
revbump: |
| 25 |
|
| 26 |
*** Ebuild technical/policy questions |
| 27 |
|
| 28 |
1. You change a package's ebuild to install an init script. Previously, |
| 29 |
the package had no init script at all. |
| 30 |
Is a revision bump necessary? Why? What about when adding a patch? |
| 31 |
|
| 32 |
|
| 33 |
So, -1, useless rebuilds is one of the biggest problems lately, it's an |
| 34 |
relatively new problem, |
| 35 |
people are revbumping packages for the simplest things like EAPI4->5 |
| 36 |
|
| 37 |
- Samuli |
Archives