I would disagree. Rolling your own is a bad idea. Source control is not
only about comparing versions and storing files away. There is also
tracking changes in source code (hopefully with useful comments per
version),
check.
> branching code (so that you don't screw up your customers by
adding new functions for the next release),
check.
controlling access (which in
Eric's case is irrelevant because he is the only developer),
check.
keeping
versions (so that you can roll back code when necessary), etc.check. (but ugh).
Okay, you got me : we used a database ;) The logic doesn't change, but yeah each of these is pretty much 1 sql change. And yeah, we have backup procedures that we get for free and that are frickin overkill for a source repository. And yeah, we don't have a serious number of developers either.
But we've ended up with a lightweight, ultra-modifiable, ultra backed up repository.
(And waay off of Eric's problem, but potential to easily tie in to timesheets, projects, bug tracking, workflow... if or when we want).
Cheers, Kurt. _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
