> The main problem with sysinstall all along has been that it is a one-off
> program. There is no glitz in writing installers, and they're only used
> once, then rarely if ever again.
The real solution is to define a little language for such maintenance
tasks, and using that as the basis for installation packaging;
something along the lines of Inferno's mush(1), which incorporate's
mk-like dependency graph manipulation rules into a shell.
This would make it easy to cleanly and elegantly automate all sorts of
system tasks; from updating configuration files from a common
repository, to installing or upgrading the base system. It could also
form the basis of something like Sun's jumpstart for FreeBSD.
Instead, we have as you say a one-off program specialized to do the
task, but in a non-extensible, and non-flexible way.
- Dan C.
(Please direct flames to /dev/null.)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
