Index of /Scripts/wizard

      Name                    Last modified       Size  Description

[DIR] Parent Directory 09-Nov-2013 17:18 - [   ] LICENSE 05-Jun-2010 16:32 1k [   ] RELEASE 05-Jun-2010 16:32 1k [   ] SCRIPTS 14-Nov-2010 11:05 1k [   ] TODO 25-Nov-2011 23:46 9k [   ] VISION 09-Oct-2009 17:58 2k [DIR] bin/ 25-Nov-2011 23:46 - [DIR] doc/ 04-Sep-2011 19:56 - [DIR] plugins/ 08-Jun-2010 02:16 - [   ] 04-Sep-2011 12:42 1k [   ] 12-Jul-2010 00:23 1k [   ] 14-Nov-2010 11:05 1k [   ] 04-Sep-2011 17:09 2k [DIR] srv/ 02-Jul-2009 02:45 - [DIR] tests/ 04-Sep-2011 13:07 - [DIR] wizard.egg-info/ 08-Jun-2010 02:17 - [DIR] wizard/ 18-Aug-2012 16:37 - [DIR] xoj/ 18-Aug-2009 03:29 -

Wizard Autoinstall

Wizard is a next-generation autoinstall management system with
an eye towards flexibility and scalability.  It is licensed
under the MIT license (you can view the license contents in


This is Python 2.6 only!

The command package

To add a new command to wizard, you need to touch the following

- bin/wizard
    Add a line describing your command in the helpstring

- wizard/command/
    Implement your command there as main(). Copy the function
    signature and scaffolding from another file; it's non-trivial
    Underscores in the module-name are referenced using dashes.

As a command file, you're expected to have a main() and parse_args()
function.  Try to keep main() one to two page function that can
be browsed for a descriptive overview of what the command does
internally.  Use helper functions to create self-documenting
code.  Don't make helper functions for one-liners.  Place
all error classes at the bottom.

Notes for repository creation

See documentation for full instructions.

- You are not going to be able to doctor a perfect repository
  from scratch.

    * If you have a simple change to a commit message, or
      something that you don't really need interactive control
      over (such as methodically rm'ing a file), git
      filter-branch is very superior.

    * 'git rebase -p -i' can be used to rewrite history interactively.
      Doing this will nuke any manual merge resolution you
      may have done (which may be a lot), thus, I highly
      recommend that you enable rerere (rerere.enabled = true)
      so that Git can automatically merge things for you.
      If the merge fails, you'll still have to reconstitute
      things manually.

    * You may want to consider using the Git sequencer, for
      which you can find a patch on the interwebs (I've never
      tried it before)

- The obvious scripts specific change that a new repository
  will have are the patches, but you should also check the
  autoinstall scripts if they do anything special.  In particular:

    - If it's a PHP application, it's probably inserting a php.ini
      file and creating symlinks to it.  Be sure to replace the
      appropriate values with placeholders WIZARD_SESSIONNAME
      and WIZARD_TMPDIR (Scripts)

    - You will probably need to generate relevant configuration
      files for each version using 'wizard prepare-config'

Design decisions

- A mass tool will plow ahead even if the subcommand throws
  Wizard errors.  Normal errors will cause us to halt
  completely.  If the error that occured is within the realm
  of possibly, and should be dealt with by manual intervention
  (or even possibly a code change), and would not cause harm
  if we continued going, we will keep going, and let the maintainer
  deal later on with the errors en masse.

  If the error is due to an error in our toolchain (and thus
  many installs can be fixed by fixing our end), we want to
  be able to re-run the mass tool with minimal fuss.

- We use the Google Python style guide.  See:
  However, we use 4-space indents, not 2-space indents.