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
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
2 matches
Mail list logo