[Openroad-users] Subversion to track component changes

[Pete Rabjohns]

Hi Folks,

 

We've been using our own source control system for years, and I was
looking into replacing this with something like subversion.

 

Basically, the individual components would be stored in export files and
checked into the source control system.

 

Client side commands would be used to 'check out' 'check in' components
from/to the developers local catalog.

 

A build process would be written which extracts the current 'branch' of
source and copies each file into a component catalog, and then calls the
makeimage command line.

 

Before I investigate this any further, I was just looking for any
gotchas that other people may have come across or any useful tips.

 

The first one that comes to mind is preventing the SCCS from modifying
the export files in case of any 'conflicts', but I think this could
probably be configured to disable multiple check outs.

 

Pete

 

 

Pete Rabjohns

Technical Manager

Atex
Email: pete.rabjohns at atex.com <mailto:pete.rabjohns at atex.com>  
Web: http://www.atex.com <http://www.atex.com/> 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://peerlessit.com/pipermail/openroad-users/attachments/20070514/4e2303f7/attachment.html