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 * [HOOK] wizard.install contains strategies for guessing variables
18 for an installation that are Scripts specific
20 * We should have `wizard install` do something intelligent about
21 prompting a user about possibilities; not everyone is going to
22 use the scripts-start wrapper.
24 * [DEFER] The mass-* commands are especially designed for Scripts,
25 so while they're ostensibly portable, they'd probably need a bit
26 of working to be easy-to-use for other people. They also rely on
27 a "versions" directory whose code exists independently of Wizard.