[ale] General Question on managing Orcad design archives

[John Mills]

Hello -

I have set up a CVS server for source code and some 'release' binaries
built from those sources. This generally seems to be working.

I am now looking into managing Orcad board layouts from the same server
and repository. I identify (with linux 'file *') primarily two groups of
types among the design files:
 *.BOM - DOS/ASCII text
 *.ONL - (ditto)
 *.opj - (ditto), and
 *.DSN - binary, as "Microsoft Office Document"
 *.DBK - (ditto)

I would expect CVS to handle the DOS/ASCII files with no problems.

However, if CVS handles those binary (*.DSN, *.DBK) types I expect it
might archive revisions by 'plugging together' succeeding binaries, with
consequent bloat as working revisions are stored. Is this correct? Is
there a cleaner way to handle these types of files with regards to
efficient storage of work-in-progress backups?

Naturally I would not expect a 'merge' operation to give sensible results
(either as to adding two workers' changes or of identifying conflicts), if
these are truly binary files.

Thanks for any general or specific comments on this problem.

 - John Mills



---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.