1 |
On Tuesday 13 October 2009 21:26:40 schism@×××××××××.org wrote: |
2 |
> On Tue, Oct 13, 2009 at 08:40:48PM -0400, Mike Frysinger wrote: |
3 |
> > USE=oldnet is documented, end of story. you're complaining about a |
4 |
> > *bug*, not lack of documentation. stop mixing the two as you're only |
5 |
> > muddling this thread. |
6 |
> |
7 |
> I don't think you are going to find anyone here stating that the USE |
8 |
> flag itself is not documented. The heart of the matter is that, not |
9 |
> only do we testers find the sweeping API changes poorly documented |
10 |
> (preventing properly testing them and starting this thread), but there |
11 |
> are many regressions, several of which are non-starters. |
12 |
> |
13 |
> Seemingly simple things like configuring static routes, setting MTUs, |
14 |
> and bringing up interfaces after configuring them have fallen by the |
15 |
> wayside for no apparent reason, and with zero documentation. Even PPP |
16 |
> interface support has been dropped with little explanation other than |
17 |
> "get that old script from mrness and hope it works". |
18 |
> |
19 |
> As far as I can tell, the new openrc network API has (and has only been |
20 |
> tested with) one extremely simple paradigm in mind: DHCP or statically |
21 |
> configured hosts on a flat, autoconfigured ethernet VLAN with only one |
22 |
> off-subnet route. That is a huge step backward. |
23 |
|
24 |
everything *you're* talking about is USE=-oldnet. no one is debating that the |
25 |
new code is regression free or overflowing with documentation. that's why |
26 |
it's disabled by default (imagine that) and issues warnings during emerge. |
27 |
the mailing list is not the place to report regressions, but fortunately |
28 |
people have reported such issues in bugzilla already. |
29 |
|
30 |
Branko is complaining about bugs in USE=oldnet about which there are no bugs |
31 |
in bugzilla. vague complaints in a mailing list isnt going to get anything |
32 |
resolved, but it seems he doesnt care anymore. so we'll have to wait until |
33 |
someone else hits the issue and actually reports a bug for us to investigate. |
34 |
-mike |