Modware Loader Development

Development model

Modware-Loader development uses git for source code management. It roughly follows this git branching model. Even for core developers and maintainers we use github pull request for code contribution and review. These are roughly the steps we follow for development ...

• Clone the development branch of repository.
• Create you own branch from development. Use the following convention for branch name ...
  • For adding new feature: feature/<branch name>
  • For refactoring: refactor/<branch name>
  • For fixing bugs: bugs/<branch name>
  • For adding documentation: documentation/<branch name> Use short but meaningful ``branch name. For example if you want to add a blast loader use feature/blast-loader```. If its something not cover here use common sense.

Developer install

This is starkly different from a regular user oriented install. It is primarily intended for authoring and developmental purpose. Skip this whole document if your sole purpose is to use the commands.

Using cpanminus

We use cpanm for installing dependencies. Use your OS's package manager or perlbrew or plenv to install it.

• Go to your project folder.
• Run cpanm -n . The -n option allows for faster install, however if you prefer run it without -n.
• It is recommended to use project specific local library path for managing dependencies. Use perlbrew, plenv or local::lib for that. For further information consult their documentation.
• cpanm will not pull optional dependencies by default. In order to install optional dependencies just use cpanm -n [module-name]