8
0
mirror of https://github.com/FirebirdSQL/firebird.git synced 2025-01-22 20:03:02 +01:00

Dynamically assign $MAJOR during packaging

This commit is contained in:
Paul Reeves 2024-07-19 11:47:12 +02:00
parent e199e5f85a
commit 59c6989ff1
2 changed files with 26 additions and 25 deletions

View File

@ -8,11 +8,11 @@ to the installation package itself, rather than
Firebird $MAJOR.$MINOR in general. In addition, these notes are
primarily aimed at users of the binary installer.
It is assumed that readers of this document are
already familiar with Firebird. If you are evaluating
Firebird $MAJOR.$MINOR as part of a migration from
Firebird 2.5 you are advised to review the
Firebird $MAJOR.$MINOR documentation to understand
It is assumed that readers of this document are
already familiar with Firebird. If you are evaluating
Firebird $MAJOR.$MINOR as part of a migration from
Firebird 2.5 you are advised to review the
Firebird $MAJOR.$MINOR documentation to understand
the changes made between 2.5 and $MAJOR.$MINOR.
@ -37,36 +37,36 @@ this package. It is especially important to verify that
fbclient.dll and gds32.dll are removed from <system32>.
See the UNINSTALL section below for more info on this.
If you have installed a beta or alpha version of
Firebird $MAJOR.$MINOR the installer will rename firebird.conf
If you have installed a beta or alpha version of
Firebird $MAJOR.$MINOR the installer will rename firebird.conf
and security3.fdb as these files are no longer compatible.
Deployment of gds32.dll
-----------------------
This compatibility library is no longer deployed into
the windows system directory by default. However it
This compatibility library is no longer deployed into
the windows system directory by default. However it
remains an option at install time.
Installation of the Guardian
----------------------------
We are hoping to phase out the Guardian. It doesn't
work with the Classic server and the binary installer
does not offer it at install time if Classic is
chosen. If SuperServer or SuperClassic are chosen
We are hoping to phase out the Guardian. It doesn't
work with the Classic server and the binary installer
does not offer it at install time if Classic is
chosen. If SuperServer or SuperClassic are chosen
it is offered but not selected by default.
Re-installation of Firebird 3
-----------------------------
The binary installer does its best to detect and
preserve a previous install. If the installer detects
firebird.conf or security3.fdb it will not offer the
option to install legacy_auth. Neither will it offer
The binary installer does its best to detect and
preserve a previous install. If the installer detects
firebird.conf or security$MAJOR.fdb it will not offer the
option to install legacy_auth. Neither will it offer
the option to set the SYSDBA password.
@ -88,9 +88,9 @@ o The service installer (instsvc) uses the same
installations. This is by design. Services exist
in a single name space.
o Be sure to install as an administrator. ie, if
using the binary installer right click and choose
'Run as administrator'. Otherwise the installer
o Be sure to install as an administrator. ie, if
using the binary installer right click and choose
'Run as administrator'. Otherwise the installer
may be unable to start the Firebird service at
the end of installation.
@ -120,7 +120,7 @@ o Uninstallation leaves five files in the install
- firebird.conf
- fbtrace.conf
- firebird.log
- security3.fdb
- security$MAJOR.fdb
This is intentional. These files are all
potentially modifiable by users and may be required

View File

@ -17,6 +17,7 @@ These notes only document the firebird specific options for a scripted
installation. Developers should refer to the full InnoSetup documentation
for a description of the other options available for a scripted install.
This can be found here:
http://www.jrsoftware.org/ishelp/
It is highly recommended that a scripted install is tested thoroughly
@ -54,7 +55,7 @@ Parameters specific to Firebird installs
HELP
Invoke this file as a help screen at installation time.
Note no / is prefixed !! Because /? and /HELP are now
used by innosetup itself to dispaly innosetup specific help.
used by innosetup itself to display innosetup specific help.
/COMPONENTS="comma separated list of component names"
@ -67,11 +68,11 @@ HELP
parameter causes Setup to automatically select a custom type. A full
install requires combining components. For example:
/COMPONENTS="ClientComponent"
/COMPONENTS="ClientComponent"
would be required for a client only install.
NOTE - If a full server install is required there is no need to
NOTE - If a full server install is required there is no need to
specify /COMPONENTS. All three are chosen by default.
@ -148,7 +149,7 @@ Parameters specific to Firebird uninstalls
firebird.conf
databases.conf
firebird.log
security3.fdb
security$MAJOR.fdb
fbtrace.conf
The assumption is that these files will be useful to users