Implemented Use Cases

• run scripts in ./bin/ from anywhere in your buildout

• run tests from anywhere in your buildout

• customize eggs, generate and apply patches

% mrsd run <script> <arg1> ...

% ./bin/<script> <arg1> ...

% mrsd test

% mrsd list

% mrsd clone

% mrsd clone <egg_name_and_version>

% cd eggs-mrsd/<egg_name_and_version>

% mrsd patch --generate

% mrsd patch --apply

Installation

mrs.developer hooks into scripts generated by buildout to inject the paths to customized eggs. You can do this manually by running mrsd hookin after scripts are (re)created by buildout, or let the mrs.developer extension handle it for you (recommended):

[buildout]
extensions = mrs.developer

The mrs.developer hook needs the mrsd command line tool available, local to your buildout or globally in your PATH (recommended).

Global install (virtualenv):

% virtualenv /path/to/mrsd/venv
% /path/to/mrsd/venv/bin/pip install mrs.developer
% ln /path/to/mrsd/venv/bin/mrsd ~/bin/mrsd -s

~/bin/ is just an example for a bin directory in your PATH.

Global install (dedicated buildout), the buildout.cfg:

[buildout]
parts = mrsd

[mrsd]
recipe = zc.recipe.egg
eggs = mrs.developer

and link it into your PATH:

% ln /path/to/mrsd/buildout/bin/mrsd ~/bin/mrsd -s

If mrsd is not in your path, the mrs.developer buildout extension will create it in ./bin/. However, in order to make full use of mrsd, it needs to be in your PATH. Don’t link the one created by the extension, use a dedicated buildout or virtualenv to install mrsd gloablly.