On Aug 3, 2013 6:04 AM, "Markos Chandras" <[email protected]> wrote: > > On Aug 3, 2013 10:06 AM, "Donnie Berkholz" <[email protected]> wrote: > > > > On 15:36 Fri 02 Aug , William Hubbs wrote: > > > All, > > > > > > This message is an announcement and a reminder. > > > > > > OpenRc-0.12 will be introduced to the portage tree in the next few days. > > > > > > If you are using ~arch OpenRc, the standard disclaimer applies: remember > > > that you might be subject to breakage. > > > > > > I do not know of any breakage personally. It does work on my system, and > > > I know of others who are using OpenRc from git successfully. Some are > > > OpenRc team members, and at least one is a Gentoo user. > > > > > > If you are not comfortable with the possibility of breakage, I recommend > > > that you make sure you do not upgrade right away. > > > > > > If, on the other hand, you are comfortable with that possibility and you > > > are willing to help us test and get rid of bugs before we go stable, > > > feel free to run ~arch. > > > > > > In other words, this is the standard Gentoo disclaimer, so consider > > > yourself warned. > > > > Man, in terms of how to phrase things, this is way wrong. > > > > If you're comfortable with your stuff breaking really? No. If you want > > to help improve Gentoo. > > > > -- > > Thanks, > > Donnie > > > > Donnie Berkholz > > Council Member / Sr. Developer, Gentoo Linux <http://dberkholz.com> > > Analyst, RedMonk <http://redmonk.com/dberkholz/> > > I am not comfortable with this either. If you think the new openrc will likely break things please mask it for a few days. Do not expect all users to read the mailing list.
I personally expect this of ~arch, and am pleasantly surprised every time I update and it still works. As WilliamH mentioned, he's not seen breakage himself, but as with anything undergoing active development, as they say, "sh*t happens". People have all sorts of setups (including myself, using a preup function to rename interfaces when using oldnet), and while they try to test everything they can, they can't reproduce every possible scenario. If you're running ~arch, you should assume it might break, and be prepared for that as a possibility. That's why we call it testing, and Debian does this in a similar manner and testing there tends to break in cute ways when they release the freeze after a release, when everything waiting in sid for months suddenly is now in testing. If you know something common will break, or repairing breakage would be a significant PITA, then yes, it should enter the tree masked (see GCC for example), otherwise, imo, entering the tree ~arch is fine. -Doug PS: I'll probably install openrc-9999 on one of my systems today, just to see if anything breaks :)
