>Don't put the patches into the distro if they aren't in the upstream.
So the distro will have to wait for a new release of the package before they could include it?
>As for Firefox, Mozilla should be encouraged to create their own
>debs and rpms. Then all users need to do is add the Mozilla
>repository to their sources list and apt-get (or yum) to install.
>It's already that easy for Windows users. I would hope that
>Linux users would have it just as easy in the future.
How is an extra step *easier*? I can't think of any distro thats not extremely niche that doesn't include Firefox in their default repositories. Mozilla also has a tendency to not support older versions of Firefox that some distros ship.
I can't possibly understand how having people that don't know much about your distro make packages for it, force you to manually add their repository to your lists, and then manually fetch it (post install) would be better than the people that know what they're doing making the package.
IMO, saying upstream should provide all packages (hell, for the application I write I don't even provide RPMs for the distro I run!) or banning distros from patching is simply a knee-jerk reaction to a quite rare occurrence.