<quote who="Chris Gianelloni"> > I want to ask the opinion of everyone. I updated Enemy-Territory > yesterday to close two bugs. In doing so, I made the decision to make > the newest version of Enemy Territory use the new full download. I have > had requests from people to have the full download, rather than the > original download + patches, as the ebuild.
Few alternative suggestions: (1) Have use flag 'patchpkg' or 'patch'. If enabled patch the package otherwise download. This is a long term solution that could be used by other packages too (although I hear you wish to avoid use flags). (2) Check what files present in distfiles. The user should fetch patch manually into distfiles to enable patching. (2) (a) If only patch file present the ebuild opts for patching. (2) (b) If only full new download present ebuild uses it. (2) (c) If both present ebuild uses full download. (3) Use an environment variable like USE_PATCH="yes". They are more environmentally friendly given the late explosion in number of use flags making them unmanageable and resulting in information overload. Adding to the thought pool. Take from it what you will. :) -- [EMAIL PROTECTED] mailing list
