Quote:
Originally Posted by Katsunami
Yeah, you know... Linux has (had?) /etc (editable text config), of which the community was very proud. Then the Gnome developers, in collaboration with Red Hat went and created dconf, which is basically a Registry for Gnome and X.org. |
I can sort of understand doing it. And X.org is a PITA to manage, and likely to go away in favor of
Wayland
Many years ago, I attended a talk at a local Unix Users Group. (
Unix user's group. Linux wasn't even a gleam in Linus Torvald's eye at the time.) The speaker was Peter Weinberger, the W in awk. He talked about the need to replace X-Windows. Asked "What will that be?" he said "I don't know. That's
your problem! We got you to where we are now. It's up to you to take the next steps."
It's finally occurring.
Quote:
|
The Linux community also prides itself on a totally modular bootup sequence, which can be changed, enhanced, and customized just by using a text editor... and then, Red Hat again (and the poisonous archdevil in the open source community, Lennart Poettering) went and created systemd.
|
There is a
lot of unhappiness about systemd, and various distros that swear blind it will never be included.
And I've already seen one Linux distro that dispenses with easily edited shell scripts and text config files and does everything in Python.
Quote:
|
Yes. It's easier than implementing one's own text-based ini-file reader/writer, or using a library the handle ini-files.
|
There are a few ini file reader/editor apps out there.
Quote:
|
There are some open source programs that can read/write SQLite databases, so if you keep to one table with settings and values, it's doable.
|
If you are comfortable at a command line, you can just to it in SQLite with SQL statements.
The Fossil devs point at a third-party GUI written in Qt called
Fuel if you want a GUI.
For the sort of thing I want to do, a single table suffices.
______
Dennis