1 |
Santiago M. Mola wrote: |
2 |
> I think that's all we need in order to know how were things when the |
3 |
> patch was added and if it needs to be pushed/tracked upstream, removed |
4 |
> in the next version of the package, etc. |
5 |
> |
6 |
> Some of us already put these kind of headers, or at least an URL to |
7 |
> upstream bug or a meaningful source of info about the patch. |
8 |
|
9 |
A short description possibly including a reference to an upstream or |
10 |
Gentoo bugreport prefixed to every epatch call should be our minimum |
11 |
standard. Working on packages whose maintainers are MIA isn't always |
12 |
that simple - but it's even worse if you have to check a number of |
13 |
patches to find out what they are for, since when they are in and what |
14 |
their status is ... |
15 |
|
16 |
> However, tracking the status of every patch since its inclusion in |
17 |
> portage until it's removed would be a huge work overhead... and I |
18 |
> doubt it's worthy. |
19 |
|
20 |
I don't think it's a huge work overhead, it'll take an additional minute |
21 |
per included patch to include a minimal description into the ebuild(s) |
22 |
and use a standardized header for the patch. Compared to the time one |
23 |
needs to spend when searching for information on that patch somewhen |
24 |
later on it's worth every minute. |
25 |
|
26 |
Tobias |