| 1 |
Thomas Sachau wrote: |
| 2 |
|
| 3 |
|
| 4 |
<SNIP> |
| 5 |
> |
| 6 |
> I disagree in this place. ~arch is called testing because it actually is about TESTING new versions |
| 7 |
> and packages. You should expect problems and you should be able to recover from them and you should |
| 8 |
> be able to use bugzilla. Else i suggest you move to a stable arch instead. |
| 9 |
> |
| 10 |
> Your arguments could make sense, if it would be about the stable tree, but forcing the testing tree |
| 11 |
> to be a second stable tree, just with newer package versions isnt our goal nor does it help anyone. |
| 12 |
> |
| 13 |
> |
| 14 |
1. Much of the time on Gentoo using of ~ packages is not user explicit |
| 15 |
choice but forced compromise. |
| 16 |
I don't remember exactly anymore what prompted me to enter openrc in |
| 17 |
package.keywords, but I surely remember having a few headaches with it. |
| 18 |
Same is with many other packages- many times using ~arch is the only |
| 19 |
answer, so 99% of the time it is used for getting some package to work |
| 20 |
and not for pure testing. |
| 21 |
Having in mind state of the matter in_real_world, I really don't think |
| 22 |
that having such things at least temporarily masked ( not to mention |
| 23 |
DOCUMENTED!) is really not overdoing it. |
| 24 |
|
| 25 |
2. About using bugzilla- how the heck was I supposed to use it without |
| 26 |
net access ? |
| 27 |
|
| 28 |
3. My main if not only argument was about at last documenting such changes. |
| 29 |
|
| 30 |
As it was done, it presented me with nasty surprise. Machine has gotten |
| 31 |
through upgrade world just fine and only after reboot it couldn't start |
| 32 |
network interfaces. Manual restart croaked with some error about python |
| 33 |
not being able to find some function. |
| 34 |
|
| 35 |
It felt exactly like a few last times when my ext4 decided to lose a few |
| 36 |
hundred essential system files. There was nothing to suggest openrc. |
| 37 |
After I lost some time reemerging system files and sifting through |
| 38 |
ebuilds, packages and scripts, that casual message here about new openrc |
| 39 |
hit me purely by chance, otherwise I would be in for much more pain. |
| 40 |
After I got system running again, I couldn't find anywhere anything at |
| 41 |
all about any substantial change in openrc. |
| 42 |
Not on bugzilla, not on openrc home page nor anywhere else. |
| 43 |
|
| 44 |
|
| 45 |
4. About filing bugzilla bug, I can't do it now, since I am in a hurry |
| 46 |
and without it I can't contribute any really useful data. |
| 47 |
Will do when I get around to it... |
Archives