Re: Control of version

In article <33B9E3D8.14A@netcomuk.co.uk>, Ian Goddard <igoddard@netcomuk.co.uk> writes >Tim Schaefer wrote: >> ><snip> >> >> It is absolutely amazing at how many sites do not have a source code >> control implementation, or how many programmers out there that do >> not use make. I know of several shops here in Florida with large >> amounts of 4GL, and the programmers do not use make, or SCCS/RCS/PVCS. >> Many defer to that sissy i4gl interface, which should be removed >> from the system. :-) I know of many who create shell scripts to >> compile ESQLC! Make is actually quite easy to use, otherwise I >> wouldn't have my digs for these other methods. There is also Microsofts' >> nmake for Win95/NT, which is extremely similar to UNIX make, and allows >> an additional feature of #if #else #endif programming. > >BTW an additional entry for your wish list. "That sissy little i4gl >interface" to produce custom runners/debuggers for r4gl/idb. > > >> If you want additional ideas, I've got make_mk, which produces makefiles >> for 4GL, and ESQL/C--to a limited degree--and grnd_mk, which attempts to >> produce a makefile for several executables in one makefile, from a flat-file >> database of executables. They are at my site, are not perfect, but can >> allow you to set up repeatable, consistent makefiles. >> > >I'll try that. My usual experience on wrestling with make is that I've >come off second best. > >Make and RCS/SCCS still don't deal with synchronising versions of code >against versions of database. Still no suggestions there, I see. > Use dbschema to dump the database schema to a flat file and then put it under SCCS. Have a master file which lists the compatible SCCS versions of ALL files on the product including the database schema file. Put that master file under SCCS as well. >Ian -- David Williams