It would be nice if, when the linux installer script detects an existing installation of firebird, to allow the user to perform an upgrade only - without changing the config files and the security database.
I did something like 'a proof of concept' like this:
- unpacked the
buildroot.tar.gz file, renamed all *.conf files to *.conf.orig and also security5.fdb to security5.fdb.orig, the re-packed it again
- changed respectively the
manifest.txt
- made small changes to the
install.sh script install-patch.txt
It seems to work OK for me, but I may have missed some more subtle details.
I chose not to create the *.conf files when installing, hoping that everything would work with the defaults. The *orig files are there as reference for anyone who would wish to change the default settings, and then the configuration files will be easier to read.
It turned out firebird.conf is required, so I created a small stub for it.
Now that I think of it (but I already uploaded the patch), this will not work as expected when overwriting existing install (not upgrading). It is still necessary to copy the .conf.orig files to .conf or at least overwrite the .conf with empty files. Anyway...
It would be nice if, when the linux installer script detects an existing installation of firebird, to allow the user to perform an upgrade only - without changing the config files and the security database.
I did something like 'a proof of concept' like this:
buildroot.tar.gzfile, renamed all *.conf files to *.conf.orig and also security5.fdb to security5.fdb.orig, the re-packed it againmanifest.txtinstall.shscript install-patch.txtIt seems to work OK for me, but I may have missed some more subtle details.
I chose not to create the *.conf files when installing, hoping that everything would work with the defaults. The *orig files are there as reference for anyone who would wish to change the default settings, and then the configuration files will be easier to read.
It turned out firebird.conf is required, so I created a small stub for it.
Now that I think of it (but I already uploaded the patch), this will not work as expected when overwriting existing install (not upgrading). It is still necessary to copy the .conf.orig files to .conf or at least overwrite the .conf with empty files. Anyway...