Slightly related to this thread -- is there any policy regarding the
format of configuration files for new software or re-writes of
existing software.
XML would be the obvious choice (it is both human and machine
readable), but I did see a recent post here that requested "anything
but XML". I can understand why someone would not like XML (not easy to
read, difficult to edit with vi without breaking the file). But one of
the things I hate about unix like OSes is that every application has a
different config file format, making writing admin tools very
difficult.
If not XML then what? Obviously the project owner gets to choose, but
in the absence of personal preferences I think it make sense for
Fedora Core project to make a recommendation so as to make the
development of admin tools easier.
Joe.
On 11/17/05, Gilboa Davara <gilboada(a)netvision.net.il> wrote:
On Thu, 2005-11-17 at 10:11 -0500, Dimi Paun wrote:
> From: "Gilboa Davara" <gilboada(a)netvision.net.il>
> > How the API will look in the end, is less important at this point.
> > Gilboa
>
> Sure, but that's the topic of this thread :) I'm not claiming
> it's the most important aspect, but it's important and it doesn't
> seem to be addressed by any of the current proposals.
>
> --
> Dimi Paun <dimi(a)lattica.com>
> Lattica, Inc.
>
Agreed.
However, there seem to be bigger discussion (in the "init observation"
thread) about whether there's a need to replace the init system to begin
with.
I agree that the init.d system is very old and slow.
However, I rather not have a C/CPP based system that I cannot edit in 3
seconds, which I want to change something.
Gilboa
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list