Re: Control of version

In article <33B340A5.4644@netcomuk.co.uk>, Ian Goddard <igoddard@netcomuk.co.uk> writes >Daniel, > >I have used RCS in the past. A recent post here described year 2000 >problems with SCCS. > >Whilst RCS or SCCS will deal with different versions of a given file >they don't, as far as I recollect, deal with file to file dependancies, >e.g. version x of one 4gl must be used with version y of some other 4gl >or version z of a .per files. I'm sure some of the commercial products, >and possibly public domain ones also, handle such issues - perhaps >someone would comment on this. The really big problem is controlling >program source against versions of the database. Anyone know of >solutions there? > >Ian > We use SCCS and have built a layer of scripts above it. All programs contain modules/forms of the form xxxxx_00.4gl xxxxx_01.4gl xxxxx_02.4gl Thus by always checking out and check in xxxxx*.4gl we ensure all modules keep the same version number. Within the MAIN function of each program is a line which reads sccs_info=".SCCS_INFO...version x.xx" from SCCS, thus by doing a strings xxxxx.4ge | grep SCCS_INFO we can get which version we use to compile a .4ge program. When a program is checked back in we prompt for an associated sql script to update the database as needed. This goes into the SCCS comments for the version change... -- David Williams