> >Nothing nailed down so-far...the "whole enchalida" is up for grabs! I'd > >especially like to see a clean, extensible, understandable method for > >setting up complex networking configurations & static routes, since we're > > Something like a meta-defninition that goes in the package (currently > /var/lib/lrp/<packagename>.*) that defines what & how to configure the > package? > > That way someone could write a screen-based configuration manager (like > Oxygen's acfg), or the web-gui, or a microwindows/nano-x configuration > manager, or whatever, and they all talk to the common backend definition? > > Or am I going too far?
No...that's exactly what I'm thinking. There should be a consistent way to configure/manage a package, so multiple front-ends can be driven w/o requiring changes to the basic package. Maybe even a set of low-level tools to deal with modifying configuration files, allowing an API level interface to configuration front-ends... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
