4 We'd like Wizard to be sufficiently general so as to not work
5 on Scripts. To some degree, it already is; Wizard can be easily
6 set up in a development type environment on a non-Scripts server.
8 Here documents Scripts specific code inside Wizard that should
11 * wizard.scripts is the location that all Scripts specific code
14 * wizard.sql does a Script's specific call to get SQL information
15 if no SQL credentials are explicitly passed.
18 - get_dir_owner performs a PTS query if normal pwd querying
20 - get_operator_name_from_gssapi requires a patch to SSH that
21 we patched support for
22 - get_operator_info consults Hesiod for more information based
24 - set_author_env guesses emails using scripts.mit.edu addresses
26 * wizard.install contains strategies for guessing variables
27 for an installation that are Scripts specific
29 * The mass-* commands are especially designed for Scripts, so while
30 they're ostensibly portable, they'd probably need a bit of working
31 to be easy-to-use for other people. They also rely on a "versions"
32 directory whose code exists independently of Wizard.