| 1 |
<quote who="Chris Gianelloni"> |
| 2 |
> I want to ask the opinion of everyone. I updated Enemy-Territory |
| 3 |
> yesterday to close two bugs. In doing so, I made the decision to make |
| 4 |
> the newest version of Enemy Territory use the new full download. I have |
| 5 |
> had requests from people to have the full download, rather than the |
| 6 |
> original download + patches, as the ebuild. |
| 7 |
|
| 8 |
Few alternative suggestions: |
| 9 |
|
| 10 |
(1) Have use flag 'patchpkg' or 'patch'. If enabled patch the package |
| 11 |
otherwise download. This is a long term solution that could be used by |
| 12 |
other packages too (although I hear you wish to avoid use flags). |
| 13 |
|
| 14 |
(2) Check what files present in distfiles. The user should fetch patch |
| 15 |
manually into distfiles to enable patching. |
| 16 |
|
| 17 |
(2) (a) If only patch file present the ebuild opts for patching. |
| 18 |
|
| 19 |
(2) (b) If only full new download present ebuild uses it. |
| 20 |
|
| 21 |
(2) (c) If both present ebuild uses full download. |
| 22 |
|
| 23 |
(3) Use an environment variable like USE_PATCH="yes". They are more |
| 24 |
environmentally friendly given the late explosion in number of use flags |
| 25 |
making them unmanageable and resulting in information overload. |
| 26 |
|
| 27 |
Adding to the thought pool. Take from it what you will. :) |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives