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