1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
|
5 |
Hi fellow Gentoo Developer ;-) |
6 |
|
7 |
An idea I got this morning, which is certainly not new, but I'd like to know |
8 |
what are/his the final word on this from your mind. |
9 |
|
10 |
What about a central config file, that would be able to generate all other |
11 |
related config... gentoo_config.xml, which when transformed using xslt, |
12 |
would produce conf.d/net, conf.d/ntp, etc... |
13 |
|
14 |
I would be interested in working on this. It looks like the way this would |
15 |
work could be similar as the today ebuild script system, where one would |
16 |
write a XSLT for each module it port inside gentoo. |
17 |
|
18 |
For example, I get in, I add an app such as xntp, I write down the xml |
19 |
stylesheet to convert |
20 |
|
21 |
<ntp> |
22 |
<servers> |
23 |
<server>name</server> |
24 |
</servers> |
25 |
</ntp> |
26 |
|
27 |
Into |
28 |
|
29 |
NTPDATESERVER=name |
30 |
|
31 |
Then the ebuild script check if a ${P}.xslt file exists and if so execute it, |
32 |
otherwise it call a function such as src_config() { }. |
33 |
|
34 |
The whole system config would then stay in /etc/gentoo.xml. |
35 |
|
36 |
People would still be able to change their config as normal because the output |
37 |
files would be present and writable. Others would be able to view their |
38 |
whole system config through a single file... |
39 |
|
40 |
I have to admit that I don't have much ideas as to what are all the advantages |
41 |
/ disadvantage of such system, I just thought it looked cool ;-) Maybe I can |
42 |
just say that it is an exercice for the mind that I left for you to try out? |
43 |
|
44 |
- -- |
45 |
|
46 |
Yannick Koehler |
47 |
|
48 |
-----BEGIN PGP SIGNATURE----- |
49 |
Version: GnuPG v1.0.6 (GNU/Linux) |
50 |
Comment: For info see http://www.gnupg.org |
51 |
|
52 |
iD8DBQE8xASLfuKOJNEyL1URAqa2AJ9jyNEZstvicKCzIERcjM5wDI4JQwCfdWph |
53 |
+xrtQnfxl7Ay19QoEofwR6c= |
54 |
=PaZx |
55 |
-----END PGP SIGNATURE----- |