On 20/08/2013 21:24, Tom Wijsman wrote: > On Tue, 20 Aug 2013 13:19:10 -0500 > William Hubbs <willi...@gentoo.org> wrote: > >> All, >> >> I'm not really sure what the answer to this problem is, so I want to >> know what the group thinks about how we can handle it. >> >> During the last release of OpenRC, I learned that people *do* run >> production servers on ~arch. > > While I don't, and asked it just because of the large amount; it > appears from some things lately, and not just OpenRC, that there is a > certain group that regards ~arch as some kind of new stable. > > This isn't solely about versions entering ~arch, but also about > versions leaving ~arch; as ~ is for testing, people should expect their > version to break and they should also expect that they cannot rely on a > version remaining in the Portage tree, that's just wrong...
As a long time user and citizen of -user I can tell you what the general feeling of arch vs ~arch there is: ~arch is plenty good enough for everything except very mission critical stuff arch has plenty old stuff in it ~arch does not break every other day, and breakage is actually surprisingly rare. And, it's usually confined to openrc/udev/systemd/baselayout and other critical packages where one just knows upfront anyway that danger may lurk ahead. Some folks like me sync daily and accept that I deal with occasional breakage maybe once a month. Usually I just mask an offending package and move on. Others wait a few days and if no reported bugs, then emerge it. I get the sense that hard masked and -9999 is the new testing, ~arch is new stuff and arch is for fuddy duddys that can't abide breakage of any kind (very much like debian stable actually). I also get the sense that arch progresses too slowly for many people. How long did we wait for MySQL-5.5 to reach arch? Folk wanted that one in stable reasonably early and mixing arch/~arch is very very bad in real life. Hence the recommendation to switch to ~arch, and it usually works out just fine. Hey, maybe you guys are doing your job in ~arch *too well*, to your own detriment :-) Something to consider? [snip] -- Alan McKinnon alan.mckin...@gmail.com
