Dale Long wrote:
> The extra package elements you are describing here might make a flexible
> way to implement a configuration template for text based and web based
> configuration.
>
> Eg: <pkg>.web or <pkg>.setup-template
Took me a minute to realize what you were saying.... but that is
(almost) doable now with the new setup package I'm putting together. In
this case, a package would use dialog for dialog boxes, and would create
a file:
/sbin/setup.d/75.mypkgconf
Which would react to parameters:
bridge|firewall|router|etc....) run stuff
name) echo "Setup my new package!"
*) std_usage....
However, what you said makes me think.... dialog is theoretically
directly replacable by Xdialog; what would it take to put Xdialog on the
box and have the dialogs show up on a remote X session? Time to go find
out....
> I am thinking of the type of display Freesco uses for its web frontend,
> but with and extensible backend to suit modules and packages and lrp.
Perhaps we should go examine? I've had a hard time figuring how
HTML-only would be flexible enough...
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
