On 05.09.2010 17:36, Brad Fanella wrote:
On Sun, Sep 05, 2010 at 09:56:29PM +0300, Ionuț Bîru wrote:
On 09/05/2010 04:54 PM, Brad Fanella wrote:
Hi everyone,
I have a few popular packages I would be interested in moving to and maintaining in [community]. However, I recall reading somewhere that AUR software that includes a patch is typically not accepted in community until the upstream developers fix/merge the patches into the software and release it. Is this correct, or am I being misled?
Thanks, Brad usually we accept patches that fixes compilation issues or functionally if the patches are accepted upstream.
we don't accept patches that extends the applications and haven't been accepted upstream
-- Ionuț I see. So as long as a patch isn't adding new features that haven't been built in the package upstream (or something similar), then it is perfectly fine to include it? Thanks for clearing things up.
Arch TUs are generally considered to be the ultimate nightmare of any upstream maintainer. We come in the night, nagging with patches until all known upstream problems are fixed. Do not stop trying to get your patches into upstream. -- Sven-Hendrik