| 1 |
I think this will be a very BAD, BAD thing to do. |
| 2 |
Imagine, you want to get a really small gentoo installation, where you do not |
| 3 |
want just anything extra... |
| 4 |
Imaging paranoid sysadmin concerned with sequrity who wants to trust |
| 5 |
absolutewly nothing. He would hate the idea that something stands between him |
| 6 |
and his conf files... |
| 7 |
Well, you get an idea. |
| 8 |
Even Mandrake does not do things this way, and for the reason. |
| 9 |
|
| 10 |
Now if you just want some frendly conf interface, there is a way to correctly |
| 11 |
implement this (just as done in Mandrake, Suse and many other distros) - |
| 12 |
create an appropriate tool (optional). That tool may even use some personal |
| 13 |
database after it parses all config files, but leave these plain-text conf |
| 14 |
files *authorative*. If you are really onto it you are welcom to create an |
| 15 |
ebuild for linuxconf or even to try to strip Mandrake tools out of their |
| 16 |
distro and create an appropriate ebuild... |
| 17 |
|
| 18 |
Another point I want to make here (on the original 1 vs many files): it is far |
| 19 |
more easier to update many files that a single big one. After all, when I do |
| 20 |
etc-update I accept changes to ~60% files reject ~30% and have to hand edit |
| 21 |
the remaining 10% only. Now, with a single file that would be about 100% :). |
| 22 |
Also (and more importantly) it is far easier to check an updates (look through |
| 23 |
diffs) to plain-text files rather than XML or anything else... |
| 24 |
|
| 25 |
George |
Archives