Development of this project is hosted on Sourceforge. The project page is:

The source code is checked in into a CVS repository on Sourceforge. To access it (read-only), follow the instructions on the CVS page.

gmodconfig is written in C++. If you're interested in browsing the code or contributing a patch, the files overview below will help to get you started. When I get a chance I'll run doxygen to produce a nifty class diagram :-)

Patch policy

In the spirit of open source software, patches that fix bugs, or add functionality in line with gmodconfig's goals, or in general improve this software are welcome. To make things go smoothly, in order for me to consider a patch for inclusion into gmodconfig's CVS repository I ask that:

  • patches be made against the latest CVS sources
  • you please use cvs diff -u to generate your patch
  • patches have a coding style consistent with the rest of gmodconfig's code
  • new code be commented
  • if existing code is modified, comments be updated accordingly
  • new strings visible to users be made i18n ready, using the underscore macro; please also follow those guidelines

Please use the Patch Manager on Sourceforge to submit a patch. Thanks!

Granting CVS write access

Sourceforge makes its CVS repositories accessible read-only to anyone. Write access to a project's CVS is granted by the project's maintainer(s). Regarding gmodconfig, CVS write access is not granted to just anyone who asks. I would like to know more about contributors before granting them the keys to the repository :-)

In general, I'd like to first see a few non-trivial patches before considering granting CVS write access. A record of positive contributions to other open source projects is also a plus.

Files overview

Note: this list of files is not complete.

  • interface.[h,cpp], support.[h,cpp], callbacks.h are generated by Glade. The Glade project files are available from CVS and the source tarballs.

  • callbacks.cpp implements the callbacks declared in callbacks.h

  • modconfmgr.[h,cpp] handles reading and writing the /etc/modules.conf file, and serves as a repository for unsaved changes.

  • modgui.[h,cpp] is where the GTK code that builds the dynamic graphic interface (the tabs) lives.

  • modinforeader.[h,cpp] handles reading module informations from XML files and from modinfo's output.

  • moduletypes.[h,cpp] defines the Module and Param classes.

  • pipereader.[h,cpp] implements an helper class that connects an Unix pipe to a C++ stream. Used to access modinfo's output.

  • gmodapp.[h,cpp] is the center of this application that glues all the rest of the code together.

  • main.[h,cpp] has the entry point to the program.

Copyright (c) 2003, Cyril Bortolato Hosted by Sourceforge: Logo