David Lutterkort wrote:
> For a human, those differences are somewhat annoying, for a program that
> reads and writes INI-style files, it's a serious issue. (That's part of
> what Augeas is addressin)
But if you use an INI format to implement the backend of a gconf/dconf/...
API, then you can fix all those decisions, you don't have to care about the
subtly different formats floating around.
Being compatible with KConfig might be an advantage (but you'd have to store
your files in .kde/share/config then ;-) ), but I don't see why you would
be expected to handle some random utility's config file format. That won't
work either if you choose another format, so I don't see how it makes sense
to use this as an argument against INI.
Kevin Kofler
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
