Couple of general version control questions...

[Philippe Lhoste]

On 02/06/2009 15:07, Richard B. wrote:
> When I commit a fix/improvement, I don't want to include the .exe,
> .dll and .pdb files, but I do when I make a public release (ie. so I can
> debug any bug reports from customers).

I don't follow you there. In many open source projects I saw, public releases are made in 
the form of an archive, including all the binary stuff which is needed. It is much easier 
to download (and faster!) than getting that particular VCS tool you use and getting files 
from the repository.
If you just keep all the released packages, it is easy to get back to a given version.

> I could add .exe, .dll and .pdb
> to the exclusion list, but then these files would not be versioned
> when I make a public release.

As a user, I wouldn't like to find .pdb files in my release, even less in the repository!
I know these are useful for debugging, but for most users they are useless... and big!
You can rarely debug on the user's computer anyway.

> I've also read that it's good practice to version compiler, lib, and
> include files, but these are stored on a different drive to my
> project/source files, so how can I commit these files with my project
> files ?

You probably can't even version the compiler because it would imply to distribute it to 
everybody getting the repository's content, which is likely to be against the EULA of the 
tool...

Just my €0.02, of course.

-- 
Philippe Lhoste
--  (near) Paris -- France
--  http://Phi.Lho.free.fr
--  --  --  --  --  --  --  --  --  --  --  --  --  --