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 * We store Wizard info inside .scripts/; this should really be
12 .wizard. This might be kind of crappy to change, though. Maybe
13 .scripts should still contain Scripts specific info, but we
14 should instantiate a .wizard directory automatically (which should
15 be ignored) that doesn't need to be created in repositories.
17 * wizard.scripts is the location that all Scripts specific code
20 * [HOOK] wizard.sql does a Script's specific call to get SQL
21 information if no SQL credentials are explicitly passed.
24 - [HOOK] get_dir_owner performs a PTS query if normal pwd
26 - [HOOK] get_operator_name_from_gssapi requires a patch to SSH
27 that we patched support for
28 - [HOOK] get_operator_info consults Hesiod for more information
30 - [HOOK] set_author_env guesses emails using scripts.mit.edu
33 * [HOOK] wizard.install contains strategies for guessing variables
34 for an installation that are Scripts specific
36 * We should have `wizard install` do something intelligent about
37 prompting a user about possibilities; not everyone is going to
38 use the scripts-start wrapper.
40 * [DEFER] The mass-* commands are especially designed for Scripts,
41 so while they're ostensibly portable, they'd probably need a bit
42 of working to be easy-to-use for other people. They also rely on
43 a "versions" directory whose code exists independently of Wizard.