On Thu, 2003-02-06 at 12:37, Lynn Avants wrote: > On Thursday 06 February 2003 11:19 am, Mike Noyes wrote: > > Lynn, > > Maybe (probably) I'm confused, but I thought one of the main advantages > > of Chad's suggestion was it avoided the use of a single file database. > > Mike, your not confused at all. > I'm a bit confused to how nothing but a directory structure containing nothing > but a 'value' is going to be parsed/sourced with onboard LEAF tools for use > in conf files w/o templates. Further, how is Joe User going to locate > something by hand if he needs to. I see a single file (not the real db) as > being very useful as a translation layer between user/application and the > db.
Lynn, Chad will probably have to correct my assumptions, but here goes. We are already using a template lrcfg/acfg that drops people to an editor when they find the function they wish to change. From what I understand of Chad's suggestion, it should be possible to generate templates for command-line/shell modification. In addition, I think his suggestion abstracts the package content from the config system, thus allowing us to update/change package systems independent of config system updates. I probably misunderstood much of this, so I'll let Chad explain the system. -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
