| 1 |
On 10/09/2017 12:55 AM, J. Roeleveld wrote: |
| 2 |
> |
| 3 |
> If that is picked up by a developer, then yes. |
| 4 |
> My experience with providing bugs with ebuilds is that they get closed |
| 5 |
> eventually due to open security bugs (fixed in supplied versions for a few |
| 6 |
> years) and lack of maintainership. |
| 7 |
> |
| 8 |
|
| 9 |
If the package is maintained, then often the most helpful thing to do is |
| 10 |
to file a bug, and then outline the reasoning behind any changes that |
| 11 |
you needed to make to the ebuild. For example, if you needed a newer |
| 12 |
version of a dependency (or a new dependency entirely), you could link |
| 13 |
to the ChangeLog entry that mentions the dependency. |
| 14 |
|
| 15 |
If you don't explain why you changed something, then the maintainer has |
| 16 |
to figure out why you did it, and that takes him just as much time as |
| 17 |
reading through the ChangeLog and doing the bump himself. And by listing |
| 18 |
your changes, you ensure that the maintainer doesn't overlook anything. |
| 19 |
|
| 20 |
If the package is *unmaintained*, then sadly, your experience is pretty |
| 21 |
typical. However, having an open bug serves as a point of collaboration |
| 22 |
for anyone else interested in the package -- and you don't know how many |
| 23 |
users have downloaded the ebuilds that are posted on the bug. Maybe |
| 24 |
everyone finds it useful even though the ebuild never gets to ::gentoo. |
Archives