🚀 go-pugleaf

"Tom" <tom@nospam.net> wrote in message 
news:455f602b@newsgroups.borland.com...
> Alan,
>
> Is there a way to have it interface with the IDE so that each time a build 
> is done, the changes
> files are added to the repository? That's been my biggest problem so far, 
> is that I'll be plugging
> along and dont' want to get interrupted to manually update files to a 
> backup. Which is why I
> went to a nightly backup, that archives about a week or so before it 
> starts over.

First, forget worrying about integration in the IDE.  If it is available, 
great.  But if not, don't let that stop you from using a revision control 
system.  The two most popular revision control systems are CVS 
(http://www.nongnu.org/cvs) and Subversion (http://subversion.tigris.org), 
both of which have Windows Explorer integration tools available, TortoiseCVS 
(http://www.tortoisecvs.org) and TortoiseSVN 
(http://tortoisesvn.tigris.org), respectively.

Second, you don't necessarily have to commit changes *every* time you do a 
build.  Instead, only commit changes when you've completed some unit of work 
that makes sense, like, for example, after adding a feature.

Third, using backups instead of revision control is cumbersome, provides you 
with practically zero history information, and is very dangerous.  They 
might be fine if your work isn't critical or if you never delete the 
backups, but as you've already discovered, if you use some kind of rotation 
scheme to save space, then you can easily lose information that you may 
never be able to get back.

Of course, once you have a revision control system in place, you should 
still keep nightly backups of your repository.  And you can safely rotate 
backups of your repository without ever losing any data.

- Dennis