I always include (apart from dpr/pas/dfm)
rc
Only the application res (binary) for the icon (Delphi recreates it otherwise).
inc
You need the cfg and/or dof for the searchpath, but if you work with many developers with many different packages installed it can be a problem because also the include/excluded packages are mentioned in those files. I decided not to include them in the CVS repository. The only thing I needed from those files was the source search path. If it is missing the error is easily found.
Also I converted all dfm files to text format. I did this because you can easily show/evalute the differences between versions.
We use WinCVS 1.3, CVSNT and Araxis in our team and a quit happy about how it all works. WinCVS 1.3 support a hierarchy of projects through the modules file which is very cool if you have projects that share code. Also very important is the .ignore file which you can check in on each directory specifying which files don't matter.
Another thing to pay attention to is that if you delete a file in WinCVS the dcu remains on the local disk. You sources will compile while they are still referencing the pas file (compiling will use the dcu) but other developers that did not have the file (or deleted it) will not be able to compile the project. We installed a macro to delete dcu with no matching pas file.
Also for some component libraries we had to include some dcu (binary) because the sources were not available.
Hope you can do something with this info.
Regards Jacco
Main Topics
Browse All Topics





by: rbohacPosted on 2004-01-30 at 07:40:27ID: 10235832
Stepping up the points.