| 1 |
On 2017-12-21 01:35, William Hubbs wrote: |
| 2 |
> ~arch *will* have breakages from time to time, sometimes major |
| 3 |
> breakages, until they are masked or fixed. We are not supposed to leave |
| 4 |
> major breakages there, but ~arch is definitely not for the faint of |
| 5 |
> heart. If you are using ~arch, you are expected to be a power user at |
| 6 |
> leasst and be able to recover if your system breaks. Production servers |
| 7 |
> should not be running ~arch at all. That's the whole reason ~arch |
| 8 |
> exists. |
| 9 |
|
| 10 |
I don't agree with this. |
| 11 |
|
| 12 |
Yes, ~arch can break sometimes so you should be familiar with masking. |
| 13 |
|
| 14 |
But on the other hand: ~arch isn't a minefield. If you add something to |
| 15 |
the repository which is keyworded you should at least know that it |
| 16 |
builds and works in the default USE flag configuration. If you don't |
| 17 |
know and there's a chance to break something badly, drop keywords or add |
| 18 |
it with a mask. |
| 19 |
|
| 20 |
Breaking ~arch because a dev was unable to test for some reason is IMHO |
| 21 |
unacceptable -- even for ~arch. That's the whole reason why |
| 22 |
keywords/p.mask exist ;-) |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Regards, |
| 27 |
Thomas Deutschmann / Gentoo Linux Developer |
| 28 |
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5 |
Archives