| 1 |
On Sat, May 11, 2013 at 12:55 PM, Ralph Sennhauser <sera@g.o> wrote: |
| 2 |
> Adopting a package to distribution specifics is perfectly valid. But |
| 3 |
> here it's about adding functionality to a package that wasn't there |
| 4 |
> before. The usual reaction in such situations is to tell users to bug |
| 5 |
> upstream about it first. |
| 6 |
|
| 7 |
Adding an init.d script is hardly adding functionality - it is merely |
| 8 |
making the package functional at all. |
| 9 |
|
| 10 |
> If an upstream bug is filed and upstream says fuck off there is still a |
| 11 |
> bug report which would meet the requirement. Maybe some other distro |
| 12 |
> even filed the bug already for us. |
| 13 |
|
| 14 |
I agree that it is a good practice, but it isn't a requirement. We |
| 15 |
don't even require package maintainers to submit bugfix patches |
| 16 |
upstream, let alone init scripts. Maintainers should certainly be |
| 17 |
encouraged to do so, but it seems like we have enough trouble |
| 18 |
following rules like "don't touch packages you don't maintain, fail to |
| 19 |
test them, and end up breaking them." |
| 20 |
|
| 21 |
Rich |
Archives