| 1 |
William Hubbs wrote: |
| 2 |
> On Tue, Oct 13, 2009 at 10:55:45PM +0200, Branko Badrljica wrote: |
| 3 |
> |
| 4 |
>> Main question is NOT whether it works for you, but whether it will break |
| 5 |
>> stuff on significant percent of other users. |
| 6 |
>> It broke on my machine, for example, and it was quite disconcerting, |
| 7 |
>> since it was at quite inconvenient moment and I had note get to any |
| 8 |
>> shred of documentation about ANY kind of substantial behaviour change of |
| 9 |
>> new openrc... |
| 10 |
>> |
| 11 |
> |
| 12 |
> The default is to use the old net.ethx style network scripts, which |
| 13 |
> still work as usual, so, that is why I said that I disagree about there |
| 14 |
> being a regression. A regression means that something worked before, |
| 15 |
> but it doesn't now, and that is not the case if you accept the defaults. |
| 16 |
> |
| 17 |
> |
| 18 |
Which I did. I don't have openrc in /etc/portage/package.use, so it was |
| 19 |
emerged with default USE flags ( if you count default as in "as set in |
| 20 |
make.conf" ). emerge -pv openrc woould emerge it as: |
| 21 |
|
| 22 |
sys-apps/openrc-0.5.1 [0.4.3-r4] USE="ncurses oldnet%* pam unicode -debug" |
| 23 |
|
| 24 |
... which means with "oldnet" flag. |
| 25 |
|
| 26 |
And whenever I tried it, it broke my system. |
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
> If you accept the defaults and it doesn't work, I will gladly agree that |
| 31 |
> there is a major regression and the package should be masked. On the |
| 32 |
> other hand, if the new network scripts do not work, I don't see that as |
| 33 |
> a show stopper. Yes, I would agree that there should be a warning about |
| 34 |
> turning off the oldnet use flag, but I don't think this warrants masking |
| 35 |
> the ebuild, unless I am missing something. If I am, definitely let me |
| 36 |
> know. |
| 37 |
I don't feel comfortable with your philosophy. It doesn't matter how |
| 38 |
obvious matters seem to you, your changes can affect many people in many |
| 39 |
situations and configurations, not necessarily allways without unforseen |
| 40 |
consequences. |
| 41 |
|
| 42 |
I understand that Gentoo is not for pussies and that you can't make an |
| 43 |
ISO-9001 procedure for every change with every user, but it would really |
| 44 |
be nice to have at least some _basic_ safety, like mentioning changes in |
| 45 |
eselect news, or at least on home page of the package. |
Archives