RE: [Firebird-devel] Firebird version and Interbase/third-party t ools compatibility for v1.0 and beyond

[Leyne, S. <sl...@at...>]

David,

> > 1 - For v1.0, the "version string" returned by the server will be
> fixed
> > as "6.2.0.xxx".  The engine and install packages will, 
> however, carry
> the
> > version number of "v1.0.0"
> 
> Will the file version resources contain 6.2.0.x or 1.x?  They 
> will need
> to be 6.2.0.x for the installer to know that the versions of the files
> that it is installing are 6.2.0.x.

The resources will have "1.0.0.x"!  The "6.2" string will only be for
the isc_info calls.


> > 2 - The Windows install packages will be changed to ensure that they
> > will overwrite any existing client libraries, regardless of version.
> > Thus, ensuring that the latest Firebird client has been installed
> > (instead of keeping the old IB 4.x/5.x/6.x version). And if possible
> the
> > install will rename the existing dll rather than deleting it.

> What about interbase.msg?  If we rename gds32.dll, shouldn't we also
> rename interbase.msg at the same time since the two files are 
> basically married?  

The names of the EXEs, DLLs will not change for v1.0 -- they will for
the next release.


> BTW, the Wise scripts always create a backup folder and put
> any replaced files in that folder.

> There is also another option to change the installer so that 
> if it finds
> a version of IB prior to 6.2.0.x, it will abort the installation and
> display a message that they previous version should be removed before
> continuing.

Of the two options, I'd be more inclined to go with the backup option.
But the uninstall option has a certain elegance, in terms of ensuring a
clean environment.


Sean