Chapter 13. Contributing Code to Lire
Prev | Part IV. Lire Developers' Conventions | Next

## Chapter 13. Contributing Code to Lire

The LogReport team invites you to contribute code to Lire. We're very happy with any code contributions which work for you: it'll very likely will make life easier for other people too! We ask you to consider some points, when writing code to get distributed with Lire.

When adding new scripts, or extending and improving current Lire code, make sure you're working with the current Lire code. (When working with old code, the bug you're working on might be fixed already by somebody else.) You can get the current code by fetching our CVS from SourceForge, using the anonymously accessible pserver:

    cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/logreport login

When prompted for a password for anonymous, simply press the Enter key.

    cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/logreport co service

See also the instructions on the SourceForge website. Alternatively, you can peek at the Lire CVS using your webbrowser.

When you'd like to change e.g. `/usr/local/bin/lr_log2report`, you'll have to hack on `cvs/sourceforge/logreport/service/all/script/lr_log2report.in`. This file will get converted to `lr_log2report` by running `./configure`. Of course, when adding scripts or extending scripts, be sure to update the scripts' manpage too.

If you'd like the LogReport team to distribute your contribution, be sure to offer it to the team under a suitable software license. Refer to the Licensing section in the Lire FAQ for details.

Once you've tested your script, you can send it too the LogReport development list on development@logreport.org. The LogReport team will be happy to ship your contribution with the next Lire release.

Prev | Up | Next
Part IV. Lire Developers' Conventions | Home | Chapter 14. Developers' Toolbox