Getting the source code

The Dune Legacy source code is packaged as a tar.bz2 archive when a release is done. But for development purposes it is best to get the latest code directly from the git repository.

Needed tools

In order to get the latest code you need a git client installed. Depending on your operating system you might try one of these:

• Linux: Just install the package git with you package manager
• Windows: TortoiseGit
• Mac OS X: GitX

Checking out/cloning the code

The git repository is hosted on sourceforge and you can get read-only access to it via

git://dunelegacy.git.sourceforge.net/gitroot/dunelegacy/dunelegacy

Thus with the commandline git client you can get the code via the following shell command:

git clone git://dunelegacy.git.sourceforge.net/gitroot/dunelegacy/dunelegacy

After the check out you might try to build the code.

To keep your local repository up to date you should run

git pull

Submitting changes

When you have modified the code (e.g. fixed a bug, implemented a feature, etc.) you might want to share your changes. This can be done via a patch file. To create one you first should make sure that you commited all changes to your local copy of the repository:

git commit -a -m "Useful commit message"

Then you can create a patch containing the difference between the repository on sourceforge and your local repository:

git format-patch origin --stdout > my-changes.patch

This patch can then be attached to a bug ticket or feature request. You might need to open a new ticket if the bug or feature was not reported before.