1 |
William Hubbs wrote: |
2 |
> On Tue, Oct 13, 2009 at 06:23:32PM +0300, Markos Chandras wrote: |
3 |
> |
4 |
>> On Saturday 10 October 2009 23:30:05 Matthias Schwarzott wrote: |
5 |
>> |
6 |
>>> On Samstag, 10. Oktober 2009, Nirbheek Chauhan wrote: |
7 |
>>> |
8 |
>>>> On Sat, Oct 10, 2009 at 6:42 PM, Alin N??stac <mrness@g.o> wrote: |
9 |
>>>> |
10 |
>>>>> On 10/9/09 7:57 PM, Matthias Schwarzott wrote: |
11 |
>>>>> |
12 |
>>>>>> * does new scripts already can do all that was possible with net.* ? |
13 |
>>>>>> |
14 |
>>>>> No. PPP is not compatible with the new scripts. |
15 |
>>>>> |
16 |
>>>> Major regression. It never pays to drop surprises on people like this. |
17 |
>>>> I *strongly* suggest masking openrc-0.5.1 until the documentation is |
18 |
>>>> updated and a news file is sent. |
19 |
>>>> |
20 |
>>> Why do you suggest masking it immediately? |
21 |
>>> Emerging it without changing any use-flags, has oldnet enabled by default, |
22 |
>>> so user gets exactly the same net init-scripts as with openrc-0.4 before, |
23 |
>>> so where is the regression that needs to be masked? |
24 |
>>> One can still use the same stuff and nobody is forced to transition to the |
25 |
>>> new network script. |
26 |
>>> |
27 |
>>> Regards |
28 |
>>> Matthias |
29 |
>>> |
30 |
>>> |
31 |
>> I agree with Nirbheek. You should always provide an updated documentation ( |
32 |
>> and a news item if necessary ) when you release a new major update of such |
33 |
>> core packages. I would like to see new openrc masked until the documentation |
34 |
>> is ready with full details about the transition to the new network init |
35 |
>> script. |
36 |
>> If you don't provide such documentation in time, you will fail to make users |
37 |
>> switch to new init script in the near future, since everybody will forget |
38 |
>> about this and will use the 'oldnet' use flag anyway. |
39 |
>> The sooner you will explain them how to migrate, the better |
40 |
>> results/feedback/updated systems you will get |
41 |
>> |
42 |
> |
43 |
> I do not agree that masking the new openrc is appropriate, since it |
44 |
> works fine with the oldnet use flag and that is the default (I upgraded |
45 |
> flawlessly and left the use flags alone). |
46 |
> |
47 |
> Maybe there should be a warning for now if you turn off the oldnet use |
48 |
> flag that warns you that the new network scripts may not work in all |
49 |
> situations. |
50 |
> |
51 |
> Then, when it comes time to migrate, you can drop the oldnet use flag |
52 |
> entirely and explain in a news item how to migrate. |
53 |
> |
54 |
> |
55 |
Main question is NOT whether it works for you, but whether it will break |
56 |
stuff on significant percent of other users. |
57 |
It broke on my machine, for example, and it was quite disconcerting, |
58 |
since it was at quite inconvenient moment and I had note get to any |
59 |
shred of documentation about ANY kind of substantial behaviour change of |
60 |
new openrc... |