On Ter, 2006-12-05 at 11:41 -0800, Florin Andrei wrote: > config-tool change <app-name> <config-key> <new-value> > > ...and presto! you just reconfigured the app. E.g.: > > config-tool change apache ServerRoot "/foo/bar" > > Or something like... > > config-tool dump <app-name> | less > > ...and, well, it's self-explanatory. > > Certain values in the <app-name> space could be reserved for system > settings. E.g.: > > config-tool change system-eth0 ip-address 192.168.2.7 > > How about this? > > config-tool -remote some.other.server.com change <app-name> \ > <config-key> <new-value> Very nice, I think Mac OS X has something like this [1]. > Several different user-level tools could be implemented, offering > different views into the same data, and different mechanisms to change > the same settings: > - a command-line tool as exemplified above > - a text-based pseudo-GUI (think Midnight Commander) > - a true GUI, based on GTK or Qt or what have you > - APIs for PHP, Perl, Python, C, Java, etc. for Web interfaces or for > direct access from within other apps > If push comes to shove, the configuration daemon could be stopped and > the XML backend (or whatever) could be edited manually by those who > really need to do that. And let's not forget that these APIs could and should provide mainloop integration like gconf does so that preferences can be automatically applied without manual daemon restarts or polling hacks. Yes even the sys V init system should completely go away and be something more like upstart[2]... I digress. Rui [1] http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFPreferences/Concepts/PreferenceDomains.html#//apple_ref/doc/uid/20001168 [2] http://upstart.ubuntu.com/
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
