Norman Rieß <nor...@smash-net.org> writes: > There was a lib update, that broke sancho a while ago. A new version of > sancho fixed this. But i had to use this new version from the developers > site, because even ~arch package was several versions lower. > Some weeks ago the oscar protocol or something was changed and pidgin > was not able to login to icq. New version fixed this instantly, but it > took a while till this version hit ~arch. Again i had to install a > program outside of portage.
This seems very varied. With some herds/maintainers/developers new versions show up in ~arch within hours of upstream release. With others ~arch can be months behind upstream even when there are bugzilla entries from users reporting that just copying the latest ebuild to the new version number works fine for them. There have even been cases where the latest version in ~arch has no longer been supported by upstream.
