1 |
On Sat, 2004-03-20 at 07:45, John Nilsson wrote: |
2 |
> 1. Standardize a configuration backend. |
3 |
> Fileformat, parsers, filesystemlocation and that stuff |
4 |
|
5 |
I note that Debian went down this exact road with something called |
6 |
"debconf". Anyone considering doing something formal in this space |
7 |
should install a Debian box somewhere and study what debconf is like. |
8 |
|
9 |
They set out with noble objectives (much the same as what you specified |
10 |
above) but ended up with something quite cryptic, hard to follow, and |
11 |
inconsistent. |
12 |
|
13 |
[Recall how people keep saying "can I see those ebuild messages again"? |
14 |
Same sort of problem] |
15 |
|
16 |
2. Convince developers to follow the standard. |
17 |
|
18 |
Which is tricky - not so much that there aren't uses for it, but rather |
19 |
the mass proliferation of packages means that only some packages use it. |
20 |
More importantly, Gentoo tends to leave configuring software alone, and |
21 |
lets the deploying sysadmin/user deal with it. Debian and RedHat (and..) |
22 |
try to automate creation of a file that may or may not be suitable to |
23 |
your needs, and then layer (in Debian's case) debconf on top of it. |
24 |
|
25 |
The difference between RedHat and Debian in this case is that on a |
26 |
RedHat system you tend to use their tools to interact with the |
27 |
configuration on an ongoing basis. While annoying to us console jockey |
28 |
types, at least its consistent. Debian, on the other hand, tries to |
29 |
accomodate both - you certainly don't revisit debconf... |
30 |
|
31 |
> 3. Interface with it |
32 |
> HTML, QT, GTK anything goes... |
33 |
|
34 |
They never got that far, which is perhaps the problem |
35 |
|
36 |
As ever, we have a lot to learn from each other. |
37 |
|
38 |
AfC |
39 |
Sydney |
40 |
|
41 |
-- |
42 |
Andrew Frederick Cowie |
43 |
Operational Dynamics Consulting Pty Ltd |
44 |
|
45 |
Australia: +61 2 9977 6866 North America: +1 646 472 5054 |
46 |
|
47 |
http://www.operationaldynamics.com/ |
48 |
|
49 |
-- |
50 |
gentoo-dev@g.o mailing list |