You want to help us?

Nice! :-)

Patches

We like patches and anybody who found a bug can submit a patch. Our mailinglist is the perfect place to discuss bugs and patches. If you want to send a patch, please test it with our trunk-repository. Stable versions are outdated for development.

When sending a patch to the mailing list, prefix the subject with [PATCH], that way we can organize our e-mails better.

How to make a patch

If you are using svn, you simply need to send the output of svn diff, the same applies to svk and git. Otherwise use diff -Naur.

Some notes for i-files

There's something you need to know before submitting a ifile to the mailing list: Linux distributions aren't all the same, they do have substantial differences that makes them incompatible in many ways, so a ifile for your system will not work on all systems.

What we need are iifiles, iifiles are the source of ifiles, they are parsed by install_service to generate ifiles. The most basical thing to know about is that paths of executables aren't all the same for every distro, so you need to enclose them with '@', that way they will be replaced by install_service with the actual path to the executable. You can take a look at our repository for examples ;).

Also, if you want to fix a bugs in a ifile, please patch the bug on the latest source iifile. We can't accept patch submissions based on ifiles, or outdated iifiles, it just takes too much more time to review and integrate them.