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
15 should be ignored) that doesn't need to be created in repositories.
17 * wizard.scripts is the location that all Scripts specific code
20 * wizard.sql does a Script's specific call to get SQL information
21 if no SQL credentials are explicitly passed.
24 - get_dir_owner performs a PTS query if normal pwd querying
26 - get_operator_name_from_gssapi requires a patch to SSH that
27 we patched support for
28 - get_operator_info consults Hesiod for more information based
30 - set_author_env guesses emails using scripts.mit.edu addresses
32 * wizard.install contains strategies for guessing variables
33 for an installation that are Scripts specific
35 * We should have `wizard install` do something intelligent about
36 prompting a user about possibilities; not everyone is going to
37 use the scripts-start wrapper.
39 * The mass-* commands are especially designed for Scripts, so while
40 they're ostensibly portable, they'd probably need a bit of working
41 to be easy-to-use for other people. They also rely on a
42 "versions" directory whose code exists independently of Wizard.