| 1 |
William Hubbs posted on Sat, 03 Aug 2013 10:28:59 -0500 as excerpted: |
| 2 |
|
| 3 |
> Markos, to answer your question, there are folks on the team, and at |
| 4 |
> least one user, using OpenRc from git without issues, so as far as I |
| 5 |
> know there shouldn't be any breakage. |
| 6 |
|
| 7 |
<waves hand> |
| 8 |
|
| 9 |
The other day in the process of filing a new openrc-9999 bug, I did a |
| 10 |
search. In several years it's only my bugs, altho IIRC there were a |
| 11 |
couple from others back when Roy was upstream. I guess pretty much |
| 12 |
everyone else running it, at least that would bother filing bugs, is on |
| 13 |
the dev team. So I'd welcome some company. =:^) |
| 14 |
|
| 15 |
I run openrc-9999 because I guess my configuration's unusual enough to |
| 16 |
trigger bugs once in awhile, and from experience once I do, it's a lot |
| 17 |
easier to track 'em down if I've only a couple commits to check since my |
| 18 |
last update. Plus the fact that I can (and religiously do) run the |
| 19 |
unpack to trigger a git pull, then run git whatchanged, BEFORE doing the |
| 20 |
actual update. So if there's a problem, I either spot it right away |
| 21 |
before I actually build and install the update, or at minimum, I have a |
| 22 |
very good idea where it is once I hit it, because I have a good idea what |
| 23 |
changed and why. |
| 24 |
|
| 25 |
Running the ~arch release version, OTOH, doesn't appear to significantly |
| 26 |
reduce the incidence of bugs compared to live-git, but there's a much |
| 27 |
bigger pile of changes in a release, and far less information about what |
| 28 |
they actually are, so I'm bug-tracing pretty much blind and that's no fun |
| 29 |
at all! |
| 30 |
|
| 31 |
So openrc-9999 ends up being the perfect fit, here. =:^) |
| 32 |
|
| 33 |
-- |
| 34 |
Duncan - List replies preferred. No HTML msgs. |
| 35 |
"Every nonfree program has a lord, a master -- |
| 36 |
and if you use the program, he is your master." Richard Stallman |
Archives