[arch-general] Upstream bugs, patches

[Arvid Ephraim Picciani]

> Even if the answer is 'yes' I think the bug and patches should still be
> forwarded. In an ideal world a packager should follow the package's
> development upstream and have some communication with it's developers.
>
> If there are lingering bugs, the project has become stagnant and there
> is no one to commit changes and release a new version then I would
> consider taking the package out of the repo altogether. Move it to
> unsupported.
>
> Another issue here is if the project has some
> philosophical/technical/other issues with the patch. There's no easy
> solution here. That's something that has to be considered on a case by
> case basis. If it's bad enough, someone might decide to fork. :D
>
> It's good to make upstream problems known. Users and developers should
> work to fix the problems from the source rather than only patching
> things locally. Imagine how many more users from all distros will
> benefit if things are patched upstream. It's the user's job as well as
> the developers' to bug upstream once he or she knows the facts.


You describe what i once thought archlinux is all about. 
Maybe my ideas are not so wrong after all?


-- 
best regards/Mit freundlichen Grüßen
Arvid Ephraim Picciani