1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 09/19/2010 09:22 PM, William Hubbs wrote: |
5 |
> On Mon, Sep 20, 2010 at 06:05:46AM +0530, Nirbheek Chauhan wrote: |
6 |
>> On Mon, Sep 20, 2010 at 5:57 AM, William Hubbs <williamh@g.o> |
7 |
wrote: |
8 |
>>> I suppose one question I need to ask is the oldnet vs newnet question. |
9 |
>>> The git repository defaults to building and installing the newnet |
10 |
>>> option, and we make oldnet the default in the ebuild. |
11 |
>>> |
12 |
>>> People migrating from stable will know the oldnet option, and this is |
13 |
>>> the only way to configure the network scripts that is actually covered |
14 |
>>> in our documentation. |
15 |
>>> |
16 |
>>> Do we want to switch the upstream repository to make oldnet the default? |
17 |
>>> |
18 |
>>> What about newnet. ??Should we keep it at all? ??If we do, should we put |
19 |
>>> it behind a use flag which would be off by default? |
20 |
>>> |
21 |
>> |
22 |
>> Is there any advantage to using newnet over oldnet? If there aren't |
23 |
>> any advantages, we should not attempt to support it (even as an |
24 |
>> optional feature). Old-net by default, no use-flag for newnet; people |
25 |
>> can use EXTRA_ECONF if they *really* want to use it. |
26 |
> |
27 |
> If I go this route, I'll probably just get rid of newnet in the next |
28 |
> release entirely. |
29 |
> |
30 |
> newnet is a single script, "network", which sets up all of the static |
31 |
> routes and static interfaces. |
32 |
> |
33 |
> It is small and simple, but the disadvantage of it is that you can't |
34 |
> stop/start a single interface. |
35 |
> |
36 |
> William |
37 |
> |
38 |
|
39 |
Why can't we keep both? There are strong advantages/disadvantages |
40 |
either way and there are users invested in both new/oldnet. I know |
41 |
this is more work on doc writers, but I don't think that will equal |
42 |
the pain users will experience being forced one way or another. |
43 |
|
44 |
- -- |
45 |
Anthony G. Basile, Ph.D. |
46 |
Gentoo Developer |
47 |
-----BEGIN PGP SIGNATURE----- |
48 |
Version: GnuPG v2.0.16 (GNU/Linux) |
49 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
50 |
|
51 |
iEYEARECAAYFAkyXO30ACgkQl5yvQNBFVTVhuQCbBG2owroUS8ZFko2oEE1ZIYgQ |
52 |
rZ0An19HgxWA9Ltat3owfIB5cvqjdRGE |
53 |
=YqFX |
54 |
-----END PGP SIGNATURE----- |