Since there are 2 or more developers, isn't it time to start using modern development tools like CVS or subversion? It would automatically keep track of revisions and help users get copies of the code.

That's a good idea. It'd make 'releases' an easy exercise also (just make a branch). Bugs and their fixes could be easily tracked.

GLAST is using dOxgen (gnu) for code management, looks impressive,
provides complete Class hierarchy, documentation etc.
(see the GLAST Science Tools pages)
Suggest to investigate it for galprop.

these are 2 differnet things : CVS is a versioning system, doxygen is an automatic code documentation tool, for C++ especially.
CVS is supposed to be phased out for subversion, I would suggest to use subversion, though my experience with it is limited...
doxygen is almost a universal standard! way to go

Johann

hello,
I have installed a SVN server of galprop on my SLAC desktop : glast-jct.slac.stanford.edu
I am still learning how to configure it properly, but it accept anonymous read only connection, so you can checkout the current v50p doing :

svn checkout svn://glast-jct.slac.stanford.edu/data1/svn/galprop galprop

I intend to make some test with one of you (Igor) to confgure the secure access for a given group of people....

I am not sure about the overall structure of the repository, and Pat probablly knows more about all that than me.... Anyway, it would be nice to have a dry run, and then settle on the system, before we make further modifications to the code, like the ones that Troy proposed.... assuming that we all agree to move to CVS or SVN.

hallo 'guest' - could you identify yourself

ooops sorry, that was Johann Cohen-Tanugi....