On Sat, 4 Sep 1999 21:39:56 -0700 Joey Hess <[EMAIL PROTECTED]> wrote:
[...]
>> 4) It should be completely transparent for who don't want to use it.
> Huh? Can run in non-interactive-use-defaults mode if desired, if that's what
> you mean.
>
No; I mean that who don't want to use the configuration
Aaron Van Couwenberghe wrote:
> It seems to me that much effort is being reproduced on this particular
> subject. I agree completely with Wichert's spec -- as I recall it was
> adapted from an RFC he found somewhere, that had been through
> implementation. That kind of testing tends to solidify a s
On Sat, Sep 04, 1999 at 09:39:56PM -0700, Joey Hess wrote:
> At least 1 through 3 are already very well laid out via the debian
> configuration management specification. See
> http://www.debian.org/~wakkerma/config6/
>
> I have a nearly-done implementation of it, too:
> http://kitenet.net/programs
[EMAIL PROTECTED] wrote:
> 1) It must have many interfaces (GUI-base, Web-based, etc.).
Check. Plain old text, dialog, gtk, web, cany others someone cares to write,
all done.
> 2) The files where the configurations are stored must be easy to edit
>with a normal text editor.
Check. Can suppor
> "Diego" == ddainese <[EMAIL PROTECTED]> writes:
Diego> Hi,
Diego> I've a proposal for a configuration tool;
[...]
Diego> My proposal is a Guile-based system similar to the emacs
Diego> configuration system: emacs has a lisp builtin interpreter
Diego> that parse arbitra
Hi,
I've a proposal for a configuration tool; IMHO the features that such
tool should have are:
1) It must have many interfaces (GUI-base, Web-based, etc.).
2) The files where the configurations are stored must be easy to edit
with a normal text editor.
3) It must be extremely flexible (more
6 matches
Mail list logo
