1 |
Michael Sullivan wrote: |
2 |
> |
3 |
> Anyway, for people like me who have the X flag enabled and might |
4 |
> accidentally hit the escape key and lose their progress in the game, I |
5 |
> downloaded the source code of tuxnes-0.75 and commented out all the code |
6 |
> segments responsible for that ESC/"quit tuxnes" behaviour and I have |
7 |
> created a patch for each of the files affected (there are three.) What |
8 |
> I want to know is, should I submit the three patches in a bug report? I |
9 |
> don't have a modified ebuild ready that says, "if the X USE flag is |
10 |
> enabled, apply the patches" - I don't really know how to safely |
11 |
> write/edit ebuilds yet. Do I even submit them to Gentoo's bugzilla, or |
12 |
> should I paddle upstream with them? What should I do? |
13 |
> |
14 |
|
15 |
In general for something like this, there are a few things to consider. |
16 |
|
17 |
Is it a Gentoo Specific problem? If yes then it's usually our bug. |
18 |
Is it a feature request or a bug? Sometimes this is a hard distinction |
19 |
to make. In this case I'd say feature (but it's debatable) |
20 |
|
21 |
Either way, is there a patch for it available. Some maintainers will |
22 |
take patches because they are useful. Usually it is a good idea to |
23 |
submit these patches upstream (gentoo devs hate having patches only in |
24 |
Gentoo, we don't want to maintain them, so bonus for us if upstream adds |
25 |
them in the next version = less work for us later). Some devs will wait |
26 |
until upstream accepts the patch before putting it in the tree (I |
27 |
usually do this). |
28 |
|
29 |
So for a non-gentoo problem upstream is usually the first place to go; |
30 |
as often as not you can get a yay or nay on a patch from upstream in a |
31 |
sane amount of time. If they say yes to it you can then file a bug in |
32 |
GEntoo and reference your upstream request, asking that we patch the |
33 |
package until upstream merges it and releases it. |
34 |
-- |
35 |
gentoo-dev@g.o mailing list |