On Sun, 2 Apr 2006, Nicolas Mailhot wrote:
Again, if you think the problem is on the user side you've already lost
it.
That's interesting.... others said the problem was on the user side... and
you are saying its on the programmers side...
The problem is on the user side
The solution is on the programmers side.
Which is why analysing the problem from the software writer POW (generic
API) won't get us anywhere
Now you are just talking double talk.
What is YOUR solution for a unversal process for managing / editing
configuration files programatically? (Let me guess, hand over eyes...
what problem??)
How can we improve revision control for system config changes (Let me
guess, isn't that what tape backups are for?).
How can we improve the documentation of what configuration changes have
been made and why. i.e. the "receipy" for a given systems functionality.
(Let me guess, isn't that what tape backups and 3 ring binders are for?).
Can we have a Linux configuration system that predictable and editable
with simple methods/tools where these methods/tools do not need to change
based on how applications decide to layout their config data (Let me
guess, NO, that is crazy talk.....)
Cheers,
Shane
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
