Menu
▾
▴
firebird-devel — List for general discussion among IB developers
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(381) |
Sep
(175) |
Oct
(261) |
Nov
(202) |
Dec
(221) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(307) |
Feb
(144) |
Mar
(140) |
Apr
(571) |
May
(652) |
Jun
(376) |
Jul
(547) |
Aug
(788) |
Sep
(475) |
Oct
(445) |
Nov
(599) |
Dec
(387) |
| 2002 |
Jan
(282) |
Feb
(348) |
Mar
(641) |
Apr
(313) |
May
(227) |
Jun
(317) |
Jul
(432) |
Aug
(775) |
Sep
(514) |
Oct
(835) |
Nov
(787) |
Dec
(680) |
| 2003 |
Jan
(960) |
Feb
(1202) |
Mar
(1114) |
Apr
(744) |
May
(538) |
Jun
(670) |
Jul
(880) |
Aug
(1123) |
Sep
(943) |
Oct
(780) |
Nov
(862) |
Dec
(747) |
| 2004 |
Jan
(929) |
Feb
(818) |
Mar
(609) |
Apr
(906) |
May
(568) |
Jun
(543) |
Jul
(555) |
Aug
(656) |
Sep
(794) |
Oct
(581) |
Nov
(626) |
Dec
(555) |
| 2005 |
Jan
(867) |
Feb
(661) |
Mar
(811) |
Apr
(674) |
May
(541) |
Jun
(603) |
Jul
(439) |
Aug
(381) |
Sep
(729) |
Oct
(693) |
Nov
(493) |
Dec
(442) |
| 2006 |
Jan
(685) |
Feb
(415) |
Mar
(567) |
Apr
(763) |
May
(452) |
Jun
(393) |
Jul
(409) |
Aug
(282) |
Sep
(259) |
Oct
(398) |
Nov
(397) |
Dec
(464) |
| 2007 |
Jan
(564) |
Feb
(304) |
Mar
(442) |
Apr
(358) |
May
(353) |
Jun
(160) |
Jul
(439) |
Aug
(250) |
Sep
(276) |
Oct
(428) |
Nov
(572) |
Dec
(221) |
| 2008 |
Jan
(354) |
Feb
(277) |
Mar
(378) |
Apr
(448) |
May
(308) |
Jun
(269) |
Jul
(281) |
Aug
(142) |
Sep
(141) |
Oct
(323) |
Nov
(341) |
Dec
(352) |
| 2009 |
Jan
(362) |
Feb
(335) |
Mar
(347) |
Apr
(190) |
May
(222) |
Jun
(346) |
Jul
(281) |
Aug
(295) |
Sep
(279) |
Oct
(610) |
Nov
(580) |
Dec
(550) |
| 2010 |
Jan
(387) |
Feb
(357) |
Mar
(365) |
Apr
(168) |
May
(132) |
Jun
(61) |
Jul
(165) |
Aug
(305) |
Sep
(351) |
Oct
(405) |
Nov
(380) |
Dec
(273) |
| 2011 |
Jan
(193) |
Feb
(136) |
Mar
(445) |
Apr
(350) |
May
(214) |
Jun
(109) |
Jul
(113) |
Aug
(145) |
Sep
(43) |
Oct
(132) |
Nov
(219) |
Dec
(257) |
| 2012 |
Jan
(237) |
Feb
(170) |
Mar
(182) |
Apr
(229) |
May
(89) |
Jun
(120) |
Jul
(203) |
Aug
(112) |
Sep
(101) |
Oct
(123) |
Nov
(186) |
Dec
(83) |
| 2013 |
Jan
(122) |
Feb
(69) |
Mar
(154) |
Apr
(126) |
May
(70) |
Jun
(82) |
Jul
(96) |
Aug
(192) |
Sep
(151) |
Oct
(134) |
Nov
(192) |
Dec
(170) |
| 2014 |
Jan
(157) |
Feb
(235) |
Mar
(338) |
Apr
(327) |
May
(283) |
Jun
(204) |
Jul
(341) |
Aug
(456) |
Sep
(211) |
Oct
(294) |
Nov
(318) |
Dec
(318) |
| 2015 |
Jan
(151) |
Feb
(204) |
Mar
(363) |
Apr
(144) |
May
(134) |
Jun
(143) |
Jul
(192) |
Aug
(122) |
Sep
(190) |
Oct
(187) |
Nov
(430) |
Dec
(240) |
| 2016 |
Jan
(177) |
Feb
(188) |
Mar
(754) |
Apr
(270) |
May
(296) |
Jun
(268) |
Jul
(107) |
Aug
(131) |
Sep
(120) |
Oct
(91) |
Nov
(135) |
Dec
(69) |
| 2017 |
Jan
(225) |
Feb
(102) |
Mar
(177) |
Apr
(154) |
May
(131) |
Jun
(53) |
Jul
(130) |
Aug
(121) |
Sep
(65) |
Oct
(92) |
Nov
(87) |
Dec
(90) |
| 2018 |
Jan
(164) |
Feb
(115) |
Mar
(97) |
Apr
(136) |
May
(324) |
Jun
(172) |
Jul
(95) |
Aug
(89) |
Sep
(93) |
Oct
(149) |
Nov
(69) |
Dec
(28) |
| 2019 |
Jan
(100) |
Feb
(205) |
Mar
(125) |
Apr
(65) |
May
(52) |
Jun
(159) |
Jul
(67) |
Aug
(119) |
Sep
(224) |
Oct
(71) |
Nov
(69) |
Dec
(123) |
| 2020 |
Jan
(151) |
Feb
(114) |
Mar
(111) |
Apr
(148) |
May
(168) |
Jun
(199) |
Jul
(70) |
Aug
(155) |
Sep
(98) |
Oct
(73) |
Nov
(88) |
Dec
(73) |
| 2021 |
Jan
(63) |
Feb
(221) |
Mar
(62) |
Apr
(101) |
May
(254) |
Jun
(60) |
Jul
(148) |
Aug
(67) |
Sep
(136) |
Oct
(165) |
Nov
(123) |
Dec
(136) |
| 2022 |
Jan
(104) |
Feb
(136) |
Mar
(67) |
Apr
(42) |
May
(65) |
Jun
(45) |
Jul
(21) |
Aug
(181) |
Sep
(53) |
Oct
|
Nov
(1) |
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Tommi P. <tom...@su...> - 2022-08-25 03:53:38
|
I’ll investigate that later. Thanks. -Tee- From: James Starkey <ji...@ji...> Sent: Wednesday, August 24, 2022 4:16 PM To: For discussion among Firebird Developers <fir...@li...> Subject: Re: [Firebird-devel] (possible) Database header Of course there should. The ODS was designed with extensibility in mind, so the initial part of the header page was sacrosanct (i.e. immutable). This was an essential part of the architecture for forward and backward compatibility. The Y-valve, by design, would pass a connection string to all available engines until one was able to open the file and determine from the database header whether it could manage that database. Since the original architecture was robust and there was no rational reason to change it, I have very little doubt that you just open the a database file, read enough of the header page to get the ODS, and proceed from there. On Tue, Aug 23, 2022 at 12:14 AM Tommi Prami <tom...@su...<mailto:tom...@su...>> wrote: Hello, I was thinking that if there is some kind of header (simple enough) in Firebird Databases and/or backup files, maybe some one could point me into the right direction. I would preferably need (mainly for installer) small tool that would check the ODS version of the DB before I try to connect into it. And depending on that, do some preprocessing if needed or make some other choices based upon that. Currently I open the database and detect ODS version that way, but it makes life bit too complicated. -Tee- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Jim Starkey |
|
From: Tommi P. <tom...@su...> - 2022-08-25 03:50:21
|
same to use our own utility, gstat needs client libraries as well as our own, so we do not gain anything. Thanks for info. -Tee- -----Original Message----- From: Tommi Prami <tom...@su...> Sent: Wednesday, August 24, 2022 10:21 AM To: For discussion among Firebird Developers <fir...@li...> Subject: Re: [Firebird-devel] (possible) Database header Dang... Try to use GStat instead. -Tee- -----Original Message----- From: Dimitry Sibiryakov <sd...@ib...> Sent: Tuesday, August 23, 2022 1:11 PM To: For discussion among Firebird Developers <fir...@li...> Subject: Re: [Firebird-devel] (possible) Database header Tommi Prami wrote 23.08.2022 5:40: > I was thinking that if there is some kind of header (simple enough) in > Firebird Databases and/or backup files, maybe some one could point me > into the right direction. No. Of course Firebird database has header page described in ods.h but it has no signature and even "fixed" part is unstable between versions. The utility must read whole fist kilobyte and try to map that data to several expected header versions checking whether several fields has sane values. -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel |
|
From: Adriano d. S. F. <adr...@gm...> - 2022-08-25 01:16:02
|
On 24/08/2022 08:45, Adriano dos Santos Fernandes wrote: > > I propose this name convention starting with Firebird 5: > Here is my updated proposal based on the discussion so far: Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x86-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x86.exe Firebird-5.0.0.2816-0-windows-x86.zip Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.exe Firebird-5.0.0.2816-0-windows-x64-withDebugSymbols.zip Firebird-5.0.0.2816-0-windows-x64.exe Firebird-5.0.0.2816-0-windows-x64.zip Firebird-5.0.0.2816-0-linux-x64.tar.gz Firebird-5.0.0.2816-0-linux-x64-debugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm.tar.gz (armv7, other?) Firebird-5.0.0.2816-0-android-arm-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-android-arm64.tar.gz Firebird-5.0.0.2816-0-android-arm64-withDebugSymbols.tar.gz Firebird-5.0.0.2816-0-linux-x86.tar.gz Firebird-5.0.0.2816-0-linux-x86-debugSymbols.tar.gz Firebird-5.0.0.2816-0-source.tar.xz Firebird-5.0.0.2816-0-macos-x64.pkg Adriano |
|
From: Adriano d. S. F. <adr...@gm...> - 2022-08-25 00:59:23
|
On 24/08/2022 09:32, Alex Peshkoff via Firebird-devel wrote: > On 8/24/22 15:03, Adriano dos Santos Fernandes wrote: >> On 24/08/2022 08:59, Mark Rotteveel wrote: >>> On 24-08-2022 13:45, Adriano dos Santos Fernandes wrote: >>>> This is our Firebird 4.0.2 released files: >>>> >>> [..] >>>> It's difficult to understand, they do not mention OS and hardware >>>> architectures are inconsistent. >>>> >>>> I propose this name convention starting with Firebird 5: >>> [..] >>>> Firebird-5.0.0.2816-0-linux-x64.tar.gz >>>> Firebird-5.0.0.2816-0-linux-x64-debuginfo.tar.gz >>>> Firebird-5.0.0.2816-0-linux-arm.tar.gz (armv7, other?) >>>> Firebird-5.0.0.2816-0-linux-arm-debuginfo.tar.gz >>>> Firebird-5.0.0.2816-0-linux-arm64.tar.gz >>>> Firebird-5.0.0.2816-0-linux-arm64-debuginfo.tar.gz >>> [..] >>> >>> In general I'm OK with this, but currently our download page claims the >>> ARM32 and ARM64 build are for Android, and not generically Linux. >>> >>> So, are they actually generically Linux, or specifically for Android? >>> >> You might be correct. >> >> Alex can certainly explain better. > > Specifically for Android. I suppose this to be reflected in the name > cause it's quite possible that we will provide arm64 builds for generic > linux. > What about our android arm for 32 bits? Should we name it arm, arm32, armv7, armv7l, other? Adriano |
|
From: Adriano d. S. F. <adr...@gm...> - 2022-08-25 00:34:40
|
On 24/08/2022 12:04, Alex Peshkoff via Firebird-devel wrote: >> >> The Linux builds are not complete builds compared to Windows pdb >> builds (e.g. config files, documentation, security database, etc are >> missing) >> > > Yep, they contain only binaries with debug-info. > Linux "debuginfo" packages contains only the debug symbols. Different than Android "withDebugInfo" packages, that have full package with debug symbols embedded in the executables/libraries. Adriano |
|
From: Adriano d. S. F. <adr...@gm...> - 2022-08-25 00:32:06
|
On 24/08/2022 12:33, Paul Reeves wrote: > On Wed, 24 Aug 2022 16:04:20 +0200 > Mark Rotteveel <ma...@la...> wrote: > >> On 24-08-2022 15:36, Dimitry Sibiryakov wrote: >>> Mark Rotteveel wrote 24.08.2022 15:32: >>>> If the term is confusing or ambiguous, it already is so in its current >>>> form. >>> >>> Yes, it is. That's why I would suggest to change that. >> >> The Windows pdb packages are complete builds though. So maybe those >> should be "debug", while the Linux builds should be "debug-symbols" or >> something like that. > > The windows pdb packages contain complete builds partly because of the > requirement that anything installable must be uninstallable. Just dropping > a bunch of pdb's into the install dir will soone or later leave a mess > behind it. > > More importantly, it is essential that the symbols exactly match the > binaries, otherwise the debugger will complain and the whole exercise will > be largely useless. Shipping a complete kit guarantees that everything will > match up and can be uninstalled easily. > > But I agree with Dimitry - we should take care to distinguish kits > containing debug symbols from actual 'Debug' builds. > But that leaves a question. Who installs the "debug" binaries? I expect people looking for this is people having a problem and wanting to understand a crash. Then they would need to overwrite their installation or install it in another place. This does not look as a good workflow. It would be easy to drop the debug symbols in their installed location. The install location already has modifiable files that is not uninstalled. If the debug symbols do not matches the executables it probably will not make much harm: - Someone put them there, updated installation and did not updated the debug symbols - Someone did a wrong job - Someone will not have a good experience with the debug - Someone will correct their poor job Adriano |
|
From: Dimitry S. <sd...@ib...> - 2022-08-24 17:59:48
|
Alexander Peshkov wrote 24.08.2022 19:06: > On 8/24/22 14:31, Dimitry Sibiryakov wrote: > > Without it services seem to be pretty useless. > > I think this to be suggested in devel and if nobody sees problems - feel > free to add a ticket, I will implement it. Ok. But I don't think that a simple hack returning only thread exit code is a right way to go. > Notice - in status vector it will be a notice that service thread failed > with exit code NNN, original message with a reason for is unknown at the > final point. It is not quite try. In the old dark days when the service thread just run an external utility and mindlessly redirect whole output to the client it was so. But nowadays the thread is doing whole work itself so it can return a proper errors, warnings and verbose messages through isc_svc_query() as soon as they happen. -- WBR, SD. |
|
From: Jiří Č. <ji...@ci...> - 2022-08-24 17:58:12
|
>> How crazy idea it would be to have even Linux builds with binaries? >> > > May be I've lost context - but we release linux builds with binaries > since the first days of the project. Sorry. I meant debug(info) builds with binaries. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ |
|
From: Alex P. <pes...@ma...> - 2022-08-24 17:01:28
|
On 8/24/22 19:33, Jiří Činčura wrote: > How crazy idea it would be to have even Linux builds with binaries? > May be I've lost context - but we release linux builds with binaries since the first days of the project. |
|
From: Jiří Č. <ji...@ci...> - 2022-08-24 16:33:17
|
How crazy idea it would be to have even Linux builds with binaries? -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ |
|
From: Paul R. <pr...@ib...> - 2022-08-24 15:34:31
|
On Wed, 24 Aug 2022 16:04:20 +0200 Mark Rotteveel <ma...@la...> wrote: > On 24-08-2022 15:36, Dimitry Sibiryakov wrote: > > Mark Rotteveel wrote 24.08.2022 15:32: > >> If the term is confusing or ambiguous, it already is so in its current > >> form. > > > > Yes, it is. That's why I would suggest to change that. > > The Windows pdb packages are complete builds though. So maybe those > should be "debug", while the Linux builds should be "debug-symbols" or > something like that. The windows pdb packages contain complete builds partly because of the requirement that anything installable must be uninstallable. Just dropping a bunch of pdb's into the install dir will soone or later leave a mess behind it. More importantly, it is essential that the symbols exactly match the binaries, otherwise the debugger will complain and the whole exercise will be largely useless. Shipping a complete kit guarantees that everything will match up and can be uninstalled easily. But I agree with Dimitry - we should take care to distinguish kits containing debug symbols from actual 'Debug' builds. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird |
|
From: Dimitry S. <sd...@ib...> - 2022-08-24 15:33:20
|
Alex Peshkoff via Firebird-devel wrote 24.08.2022 17:00: > Sorry, but they are created by 'cp' command ;) One can run them directly. Wow. That's crazy. -- WBR, SD. |
|
From: Mark R. <ma...@la...> - 2022-08-24 15:06:35
|
On 24-08-2022 17:00, Alex Peshkoff via Firebird-devel wrote: > On 8/24/22 17:10, Dimitry Sibiryakov wrote: >> Alex Peshkoff via Firebird-devel wrote 24.08.2022 16:06: >>> Same for linux - not stripped binaries provided. >> >> Nope. Firebird-debuginfo-4.0.2.2816-0.amd64.tar.gz contains only >> extracted debug symbols, not binaries. >> > > Sorry, but they are created by 'cp' command ;) One can run them directly. Nonetheless, those Linux archives are not complete builds. Mark -- Mark Rotteveel |
|
From: Alex P. <pes...@ma...> - 2022-08-24 15:04:55
|
On 8/24/22 17:14, Mark Rotteveel wrote: > On 24-08-2022 16:06, Alex Peshkoff via Firebird-devel wrote: >> On 8/24/22 17:04, Mark Rotteveel wrote: >>> On 24-08-2022 15:36, Dimitry Sibiryakov wrote: >>>> Mark Rotteveel wrote 24.08.2022 15:32: >>>>> If the term is confusing or ambiguous, it already is so in its >>>>> current form. >>>> >>>> Yes, it is. That's why I would suggest to change that. >>> >>> The Windows pdb packages are complete builds though. >> >> Same for linux - not stripped binaries provided. > > The Linux builds are not complete builds compared to Windows pdb > builds (e.g. config files, documentation, security database, etc are > missing) > Yep, they contain only binaries with debug-info. |
|
From: Alex P. <pes...@ma...> - 2022-08-24 15:01:12
|
On 8/24/22 17:10, Dimitry Sibiryakov wrote: > Alex Peshkoff via Firebird-devel wrote 24.08.2022 16:06: >> Same for linux - not stripped binaries provided. > > Nope. Firebird-debuginfo-4.0.2.2816-0.amd64.tar.gz contains only > extracted debug symbols, not binaries. > Sorry, but they are created by 'cp' command ;) One can run them directly. |
|
From: Mark R. <ma...@la...> - 2022-08-24 14:14:59
|
On 24-08-2022 16:06, Alex Peshkoff via Firebird-devel wrote: > On 8/24/22 17:04, Mark Rotteveel wrote: >> On 24-08-2022 15:36, Dimitry Sibiryakov wrote: >>> Mark Rotteveel wrote 24.08.2022 15:32: >>>> If the term is confusing or ambiguous, it already is so in its >>>> current form. >>> >>> Yes, it is. That's why I would suggest to change that. >> >> The Windows pdb packages are complete builds though. > > Same for linux - not stripped binaries provided. The Linux builds are not complete builds compared to Windows pdb builds (e.g. config files, documentation, security database, etc are missing) Mark -- Mark Rotteveel |
|
From: Dimitry S. <sd...@ib...> - 2022-08-24 14:10:31
|
Alex Peshkoff via Firebird-devel wrote 24.08.2022 16:06: > Same for linux - not stripped binaries provided. Nope. Firebird-debuginfo-4.0.2.2816-0.amd64.tar.gz contains only extracted debug symbols, not binaries. -- WBR, SD. |
|
From: Alex P. <pes...@ma...> - 2022-08-24 14:06:55
|
On 8/24/22 17:04, Mark Rotteveel wrote: > On 24-08-2022 15:36, Dimitry Sibiryakov wrote: >> Mark Rotteveel wrote 24.08.2022 15:32: >>> If the term is confusing or ambiguous, it already is so in its >>> current form. >> >> Yes, it is. That's why I would suggest to change that. > > The Windows pdb packages are complete builds though. Same for linux - not stripped binaries provided. > So maybe those should be "debug", while the Linux builds should be > "debug-symbols" or something like that. > > Mark |
|
From: Mark R. <ma...@la...> - 2022-08-24 14:04:38
|
On 24-08-2022 15:36, Dimitry Sibiryakov wrote: > Mark Rotteveel wrote 24.08.2022 15:32: >> If the term is confusing or ambiguous, it already is so in its current >> form. > > Yes, it is. That's why I would suggest to change that. The Windows pdb packages are complete builds though. So maybe those should be "debug", while the Linux builds should be "debug-symbols" or something like that. Mark -- Mark Rotteveel |
|
From: James S. <ji...@ji...> - 2022-08-24 13:46:18
|
Of course there should. The ODS was designed with extensibility in mind, so the initial part of the header page was sacrosanct (i.e. immutable). This was an essential part of the architecture for forward and backward compatibility. The Y-valve, by design, would pass a connection string to all available engines until one was able to open the file and determine from the database header whether it could manage that database. Since the original architecture was robust and there was no rational reason to change it, I have very little doubt that you just open the a database file, read enough of the header page to get the ODS, and proceed from there. On Tue, Aug 23, 2022 at 12:14 AM Tommi Prami <tom...@su...> wrote: > Hello, > > > > I was thinking that if there is some kind of header (simple enough) in > Firebird Databases and/or backup files, maybe some one could point me into > the right direction. > > I would preferably need (mainly for installer) small tool that would check > the ODS version of the DB before I try to connect into it. And depending on > that, do some preprocessing if needed or make some other choices based upon > that. > > Currently I open the database and detect ODS version that way, but it > makes life bit too complicated. > > > > -Tee- > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel > -- Jim Starkey |
|
From: Dimitry S. <sd...@ib...> - 2022-08-24 13:36:20
|
Mark Rotteveel wrote 24.08.2022 15:32: > If the term is confusing or ambiguous, it already is so in its current form. Yes, it is. That's why I would suggest to change that. -- WBR, SD. |
|
From: Mark R. <ma...@la...> - 2022-08-24 13:32:43
|
On 24-08-2022 14:50, Dimitry Sibiryakov wrote: > Dmitry Yemanov wrote 24.08.2022 14:47: >>> I would unify the `pdb`, `debuginfo`, etc. into simple `debug` suffix. >> >> Agreed. > > And better to keep "debuginfo" verb, IMHO to prevent confusion after > expectation to find "a debug build" in "debug" package. What confusion, debuginfo packages are already listed as a "Debug build" on the download page. If the term is confusing or ambiguous, it already is so in its current form. In other words, consolidating it under the term "debug" shouldn't be a problem. Mark -- Mark Rotteveel |
|
From: Alex P. <pes...@ma...> - 2022-08-24 13:24:49
|
On 8/24/22 15:03, Adriano dos Santos Fernandes wrote: > On 24/08/2022 08:59, Mark Rotteveel wrote: >> On 24-08-2022 13:45, Adriano dos Santos Fernandes wrote: >>> This is our Firebird 4.0.2 released files: >>> >> [..] >>> It's difficult to understand, they do not mention OS and hardware >>> architectures are inconsistent. >>> >>> I propose this name convention starting with Firebird 5: >> [..] >>> Firebird-5.0.0.2816-0-linux-x64.tar.gz >>> Firebird-5.0.0.2816-0-linux-x64-debuginfo.tar.gz >>> Firebird-5.0.0.2816-0-linux-arm.tar.gz (armv7, other?) >>> Firebird-5.0.0.2816-0-linux-arm-debuginfo.tar.gz >>> Firebird-5.0.0.2816-0-linux-arm64.tar.gz >>> Firebird-5.0.0.2816-0-linux-arm64-debuginfo.tar.gz >> [..] >> >> In general I'm OK with this, but currently our download page claims the >> ARM32 and ARM64 build are for Android, and not generically Linux. >> >> So, are they actually generically Linux, or specifically for Android? >> > You might be correct. > > Alex can certainly explain better. Specifically for Android. I suppose this to be reflected in the name cause it's quite possible that we will provide arm64 builds for generic linux. > I'm also not sure about arm64 vs aarch64 differences. That's "serious" difference - exactly like between amd64, x86_64 and x64 :) |
|
From: Dimitry S. <sd...@ib...> - 2022-08-24 12:51:21
|
Dmitry Yemanov wrote 24.08.2022 14:47: >> I would unify the `pdb`, `debuginfo`, etc. into simple `debug` suffix. > > Agreed. And better to keep "debuginfo" verb, IMHO to prevent confusion after expectation to find "a debug build" in "debug" package. -- WBR, SD. |
|
From: Dmitry Y. <fir...@ya...> - 2022-08-24 12:48:05
|
24.08.2022 15:35, Jiří Činčura wrote: > I would unify the `pdb`, `debuginfo`, etc. into simple `debug` suffix. Agreed. Dmitry |
189 messages has been excluded from this view by a project administrator.
