On 12/23/2009 11:36 PM, Duncan wrote:
~arch does mean more and faster updates and that you should be prepared to resort to an alternate boot image, live/rescuecd or the like, in ordered to fix things if necessary, but that's a good idea in any case. And at least a package is normally tested to work on the developer's ~arch system before it's keyworded ~arch, even if it's not tested to the degree that stable is. But a half-stable half-~arch system is a no-man's- land, really not tested, nor practically testable since there's so many possible variants, at all. So if you're running more than a very limited set of ~arch packages (with few dependencies), I'd definitely recommend ~arch over stable with many ~arch packages. At least that's known to work on the dev's full ~arch system, something that cannot be said of a half-way ~arch installation.
But the only way to be sure that an ~arch plays nicely with the currently stable packages is to *not* go full ~arch. With full ~arch, you only knows that the package plays well with the latest version of all packages; but you don't know how it performs with the stable tree.
