1 |
On 06/08/2013 00:09, Robin H. Johnson wrote: |
2 |
> I'm replying the start of this thread, rather than picking a single |
3 |
> person to respond to. I DO want more brainstorming on ideas for the |
4 |
> naming of the package, and I think people need to cast a wider net for |
5 |
> naming ideas. |
6 |
> |
7 |
> I'm most certainly not planning to get rid of the package whatsoever, |
8 |
> many of my systems have complex configurations that are made MUCH easier |
9 |
> with oldnet than any other network configuration system I have found. |
10 |
> |
11 |
> Goals of gentoo-oldnet: |
12 |
> - Make oldnet functionality available to users of other init systems |
13 |
> [1][2] |
14 |
> - If a package upstream is forcing you towards systemd, you shouldn't |
15 |
> have to lose other very useful packages. |
16 |
> - Seperate out development cycle from core OpenRC |
17 |
> - oldnet accounts for more than 30% of OpenRC bugs, and a large |
18 |
> fraction of the codebase. |
19 |
> |
20 |
> History of the oldnet name: |
21 |
> - It's only called oldnet because when Roy introduced 'newnet', what we |
22 |
> consider to be 'oldnet' didn't actually have a separate name. |
23 |
> |
24 |
> Various proposed names (in no specific order): |
25 |
> - openrc-oldnet (implies OpenRC, and has 'old'). |
26 |
> - openrc-gentoo-net (implies OpenRC) |
27 |
> - gentoo-networking (does this mean newnet is here too?) |
28 |
> - gen-net (ditto) |
29 |
> - netrc (conflicts) |
30 |
> - opennetrc (implies OpenRC) |
31 |
> - 'net run control' (hard to search) |
32 |
> - 'net run configuration' (hard to search) |
33 |
> - multi-net (conflicts) |
34 |
> - netctl (conflicts) |
35 |
> - netcfg (conflicts) |
36 |
> - netconf (conflicts) |
37 |
> - enet (conflicts) |
38 |
> - posixsh-netconf (conflicts netconf) |
39 |
> - nettool (conflicts) |
40 |
> - netcfgtool (conflicts) |
41 |
> - posixnet (conflicts) |
42 |
> - shnettool |
43 |
> |
44 |
> Naming goals: |
45 |
> - Should describe what it does |
46 |
> - Does NOT have a name conflict as verified by Google. |
47 |
> - Does NOT imply OpenRC. |
48 |
> - Implying Gentoo is fine, as it's where the package comes from. |
49 |
> - Should drop 'old' |
50 |
> |
51 |
> I think we should focus on the first goal the most: |
52 |
> "oldnet is a network configuring tool in pure POSIX shell" |
53 |
> So we probably want the substring 'net' somewhere in there. Beyond that, |
54 |
> all suggestions are welcome. |
55 |
> |
56 |
> [1] There was a failed GSOC project that I mentioned several years ago, |
57 |
> that was to support ALL openrc style init.d scripts on Upstart, so |
58 |
> oldnet would have worked implicitly. Unfortunately the student didn't |
59 |
> actually do ANY work. |
60 |
> |
61 |
> [2] The configuration itself ends up broken into two parts: |
62 |
> - directives that control the startup dependency tree. |
63 |
> - directives that control the actual configuration. |
64 |
> The former will need to be interoperable or exported to other init |
65 |
> systems in some way (hopefully dynamically), the latter can stay the |
66 |
> same. |
67 |
> |
68 |
|
69 |
|
70 |
The software was originally called "net", right? Perhaps not officially, |
71 |
but certainly colloquially. |
72 |
|
73 |
Why not just keep the name "net" and leave other newer systems to come |
74 |
up with their own names? |
75 |
|
76 |
I do agree that modifiers "old" and "new" are bad ideas - they come |
77 |
about because of the environment and no the software itself. |
78 |
|
79 |
-- |
80 |
Alan McKinnon |
81 |
alan.mckinnon@×××××.com |