GNOME Commander

A powerful file manager for the GNOME desktop environment

Dev Development

This page contains information about hacking and contributing to the GNOME Commander project. We encourage anyone to contribute with code, translations, bugreporting, new useful ideas, or just give some quality feedback that also is quite important.

If you would like to get involved and don't know where to start, have a look especially into the TODO file. This file gives a hint on what we are working on, or like to work on, and maybe appreciate some community efforts on. You are also welcome to sign up on our mailing lists and take part in discussions and development. If you are keen on fixing open bugs, have a look at our Bugzilla page.

Current plans

The team behind GCMD is currently working on switching from obsolete libraries, e.g. from gnome-vfs to gvfs/GIO. This is a major task and, thus, will take some time.

Future plans

In the future, the team behind GCMD are will further enhance python plugin support. Plugins should be dropped in the ~/.gnome-commander/plugins directory. The work on supporting meta-data also continues. The plan is to add this functionality to the searchtool, custom columns and the internal viewer.

Git Git Repository

The official Git repository of GNOME Commander is registered on Gnome.org, but there exists also a fork at GitHub.

Branches and Versions

GNOME Commander is being developed in several branches:

The version numbers (major, minor and micro) follow the standard of odd and even versioning. Even numbers are stable versions, that are intended for all-day use. Odd versions are development versions. The version number is stored as git-tags in the git repository. To see all of them, just type git tag. The current one is also stored in the first line of configure.ac.

To check out the GCMD repository to your local hard disc, enter the following commands:

The instable master branch:
git clone git://git.gnome.org/gnome-commander

The current stable branch:
git clone -b gcmd-1-6 git://git.gnome.org/gnome-commander

If you already cloned the repository, run git pull inside the gnome-commander directory to get the latest code revision. To switch between the branches, run git checkout $BRANCH.

Tips for working with Git

Source code Building from source

First, check out the source code as described in the previous section. The next step is the usual ./autogen.sh && make && sudo -i make install procedure, which should work like a charm. If you are building the code from an unpacked tar archive use ./configure instead of ./autogen.sh.

When you install Gnome Commander manually the first time and you discover some errors like /configure: line 4721: GLIB_GSETTINGS: command not found or something similar you have to install some dependencies. If you are using Ubuntu you can find out which dependencies this are by looking inside the Gnome Commander Dockerfile (see below). The first RUN command contains all the apt-get commands for the required libraries.

Building GCMD in Dockerfile

There exists a Dockerfile for compiling GCMD in an Ubuntu environment. Start building it with the command sudo docker build . inside the top directory of the GCMD repository.

Contributing Contributing by Developing

If you want to contribute, send in patches, having some useful idea or just some feedback then you are welcome to contact us or you can make a pull request on GitHub against the GCMD repository.

If you have some good ideas for stuff that you want to see in this program, check the TODO file first before sending a message to the mailing lists.

If you want to submit a patch via email:

Contributing by TranslatingContributing by Translating

The current status of all project translations can be found at GNOME's Damned Lies. For adding a new translation simply download the initial potfile of the master branch and start translating by renaming the file to LL.po (replace "LL" with your language code, see the complete list of language codes). Or take an already existing po file from the list on the page given above.

Here you will find the recipe on how to contribute with your new or updated translation:

  1. Get a fresh copy of the program source (either from Git or snapshot)
  2. Unpack it and run ./autogen.sh.
  3. Update proper LL.po file: go into the po directory and run intltool-update LL.

You may find translation compedia to be quite handy as a reference. You can download some po files from other projects and create such a compedium by: msgcat -o compendium-LL.po *.po.

There are several translation tools available. Some of them are: Poedit and Gtranslator.

Have a look at l10n.gnome.org if you want to start translating for more projects than just GCMD.

From time to time check strings marked for translation. Therefore, create updated po/gnome-commander.pot with make check. Then search for incorrect translations:
podebug --format='[i18n]' --input po/de.po > output.po.
Now in the output file all found strings for translation are marked with a [i18n] tag. Then you have to start GCMD with this created po-file.

Making a releaseMaking a release


Testing/Creating a Gentoo ebuild

Hacking Hacking documents


To top of page

 
Valid html 4.01 Strict!


Background image by joanamr (CC-BY-NC-SA)