We need to consistently handle the situation, in regarding to multiple OS and different deploy of ICU, so CORE-6215 seems not the way to go IMO.
It's easy to make a standard subdirectory inside Firebird tree to put the *.res files and automatically call setenv in the engine start before load ICU. However it will not work in embedded if the application previously loaded ICU (the same DLLs used in Firebird). Maybe this is not important and in the worst case application developer may explicitly call setenv at appropriate moment. We also need a good way to release: 1) every time zone table update at our website 2) release the latest table with every Firebird release This could be done downloading the appropriate ICU tzdata *.res files and commiting as a zip to our github (in FirebirdSQL/firebird, in every supported branches). Then build/package scripts would put that files in the right place of distribution kits. Our website could link to the latest zip (master branch) of our github's tzdata. Opinions? On 28/12/2019 04:46, Mark Rotteveel wrote: > I have created two issues to address this: > > - Update tzdata: http://tracker.firebirdsql.org/browse/CORE-6214 > - Include icupkg: http://tracker.firebirdsql.org/browse/CORE-6215 > > I would recommend that the first one is done before releasing Firebird > 4 beta 2. > > Mark > > On 06/07/2019 11:47, Mark Rotteveel wrote: >> Currently, the Firebird 4 snapshots still include TZ database 2018e. >> The latest version at this time is 2019b (2019-07-01), although ICU >> doesn't seem to have added it yet on >> https://github.com/unicode-org/icu-data/tree/master/tzdata/icunew. >> >> What is the plan to keep this up-to-date for releases? >> >> Another thing I was wondering about, if I update manually, is there a >> default location that will work for the `res` files? The instruction >> says "The easiest way to update is downloading the *.res files in a >> directory and set ICU_TIMEZONE_FILES_DIR environment variable >> pointing to it.", but that isn't always an option when running >> Firebird as a service on Windows. >> >> I tried putting them in the root Firebird folder, but that doesn't >> work without setting the environment variable. And integrating them >> into icudt63l.dat requires access to the icupkg tool which doesn't >> seem to be readily available except through building it yourself, >> which isn't a common action on Windows. >> >> Mark > > Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
