Re: Control of version

Tim Schaefer wrote: <snip> > > As for file-dependency chaining, this is something that I'd handle > in makefiles, but I learn new things every day. :-) > Make handles the fact that one file depends on another but how do you make it handle the fact that file2.4gl version 1.4 needs version 1.2 of file2.4gl and version 1.3 of file3.per? Does PVCS do this? In RCS you're simply reduced to putting it in the version description. Defining the version of the database structure is even trickier. You could run dbschema after every change and give that a version number - but in practice migrating from one version to another might involve some ALTER TABLES and even some UPDATES (ALTERing a table to add a non-null column isn't a single step process and will involve an UPDATE that dbschema can't even capture). Such files must be applied to a specific version of the database. I'm currently working on a site which received updates of a 3rd party application every few weeks. I haven't counted the number of source & executable files in the system but it runs into thousands! Some of these releases involve changes to the database structure. Some of the code releases may include changes already installed at the site as bug-fixes made in advance of the general code release. This makes me a bit sensitive to these issues. The software house concerned seems to have nothing like RCS or SCCS in place at all! Ian