On Sunday 02 February 2003 08:11 pm, Matt Schalit wrote: <snip> > I) central config-db > II) package system > III) gui admin program > > > > I can be done alone, even with the current lrcfg and lrpkg. > II is dependant on I being done. > III is dependant on II. > > > Can we concur on the above? I think it's important to get > our foundation in order. I think the dependancies are more > logical than hard and fast rules. I don't want to have to > rewrite a gui admin program if a new package system comes > out a month later.
That looks correct to me. A roadmap is absolutely necessary. <snip with other submitted material> > 5. post-config done on separate OS via LEAF based perl/weblet/cgi > apps. 6. post-config done on separate OS via local based perl/www/cgi > apps. 7. post-config done on separate OS via local Java app. > 8. post-config done on separate OS via local Python app. > > 9. post-config done on LEAF using terminal based ascii gui, like > Oxygen. > > 10. Make pre-config and post-config into one app. I don't believe Perl is a feasible option on the LEAF box for CGI, especially when Jscript and shell-script are and wouldn't require an interpreter. Just for clarification, is Java being suggested instead of Jscript? My reasoning is determined by the need for an interpreter. Added options: 5a) post-config done on separate OS via LEAF based shell-script/www/cgi. 5b) post-config done on separate OS via LEAF based Jscript/www/cgi. 9a) post-config done on LEAF using script. 9b) post-config done on LEAF using editor (hand). Thank-you for putting this together Matt, I would imagine it can consolidate some discussion. -- ~Lynn Avants Linux Embedded Firewall Project developer http://leaf.sourceforge.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
