Re: [Firebird-devel] Improve release filenames
> As the Intel platforms will be the *huge* majority, what about this: > > win32 | win64 |win64-arm > > or this: > > win32-x86 | win64-x86 | win64-arm > > or just: > > win32 | win64-x86 | win64-arm That seems pretty inconsistent (in regards to other filenames). -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25-08-2022 15:13, Stefan Heymann wrote: I propose this name convention starting with Firebird 5: Firebird-5.0.0.2816-0-windows-x86-pdb.exe Firebird-5.0.0.2816-0-windows-x86-pdb.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-pdb.exe Firebird-5.0.0.2816-0-windows-x64-pdb.zip Firebird-5.0.0.2816-0-windows-x64.exe Firebird-5.0.0.2816-0-windows-x64.zip [...] I'd like to suggest you use win32 and win64 instead of x86 and x64. Or, it you want to keep the "windows" prefix, use window-32 and windows-64. For me as a Windows user this would be much more logical (the 86 comes from the 80*86 processor, the 64 comes from 64 bits, so it's not consistent from the beginning). The proposed naming has the benefit it is consistent across platforms. That is: Firebird---[-qualifier]. I don't see the need, nor the point to deviate from this for Windows. Mark -- Mark Rotteveel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
>> > I'd like to suggest you use win32 and win64 instead of x86 and x64. Or, it >> > you want to keep the "windows" prefix, use window-32 and windows-64. >> > For me as a Windows user this would be much more logical (the 86 comes >> > from the 80*86 processor, the 64 comes from 64 bits, so it's not >> > consistent from the beginning). > In the past win32 and win64 was good but now Windows exists for ARM64. > x86, x(86-)64, arm64, etc. are more clear. But I am not a core developer just > a user. :-) As the Intel platforms will be the *huge* majority, what about this: win32 | win64 |win64-arm or this: win32-x86 | win64-x86 | win64-arm or just: win32 | win64-x86 | win64-arm Regards Stefan Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
> In the past win32 and win64 was good but now Windows exists for ARM64. > x86, x(86-)64, arm64, etc. are more clear. But I am not a core developer > just a user. :-) Same for me. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
2022.08.25. 15:13 keltezéssel, Stefan Heymann írta: I'd like to suggest you use win32 and win64 instead of x86 and x64. Or, it you want to keep the "windows" prefix, use window-32 and windows-64. For me as a Windows user this would be much more logical (the 86 comes from the 80*86 processor, the 64 comes from 64 bits, so it's not consistent from the beginning). In the past win32 and win64 was good but now Windows exists for ARM64. x86, x(86-)64, arm64, etc. are more clear. But I am not a core developer just a user. :-) Gabor Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
> I propose this name convention starting with Firebird 5: > Firebird-5.0.0.2816-0-windows-x86-pdb.exe > Firebird-5.0.0.2816-0-windows-x86-pdb.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-pdb.exe > Firebird-5.0.0.2816-0-windows-x64-pdb.zip > Firebird-5.0.0.2816-0-windows-x64.exe > Firebird-5.0.0.2816-0-windows-x64.zip > [...] I'd like to suggest you use win32 and win64 instead of x86 and x64. Or, it you want to keep the "windows" prefix, use window-32 and windows-64. For me as a Windows user this would be much more logical (the 86 comes from the 80*86 processor, the 64 comes from 64 bits, so it's not consistent from the beginning). Best Regards Stefan -- Stefan Heymann, Tübingen, Germany Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25-08-2022 12:38, Dimitry Sibiryakov wrote: Dmitry Yemanov wrote 25.08.2022 12:34: 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 Looks good to me. Is this zero after build number necessary? We have had -1 releases, e.g. https://firebirdsql.org/en/firebird-4-0-0/#Win32 (Firebird-4.0.0.2496-1-Win32.exe), so for consistency, either it should always be included, or we should ditch this package revision (or whatever we should call it) entirely. Mark -- Mark Rotteveel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25/08/2022 07:38, Dimitry Sibiryakov wrote: > > Is this zero after build number necessary? > It's packaging number. We had this type of problem in Windows build in the past, where retag was not necessary and the package number was increased. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25/08/2022 07:19, Mark Rotteveel wrote: > On 25-08-2022 03:15, Adriano dos Santos Fernandes wrote: >> 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 > > Sounds OK. On suggestion: use "with-debug-symbols" and "debug-symbols", > but that is just because I'm a bit allergic to capitals in filenames ;) > Me too, but I want to use dashes to separate components in this case, and then it would be inconsistent have a single information spread into multiple parts. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
Dmitry Yemanov wrote 25.08.2022 12:34: 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 Looks good to me. Is this zero after build number necessary? -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
25.08.2022 04:15, Adriano dos Santos Fernandes wrote: 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 Looks good to me. Dmitry Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 25-08-2022 03:15, Adriano dos Santos Fernandes wrote: 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 Sounds OK. On suggestion: use "with-debug-symbols" and "debug-symbols", but that is just because I'm a bit allergic to capitals in filenames ;) Mark -- Mark Rotteveel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On 24/08/2022 12:33, Paul Reeves wrote: > On Wed, 24 Aug 2022 16:04:20 +0200 > 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. 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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
>> 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/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
How crazy idea it would be to have even Linux builds with binaries? -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
On Wed, 24 Aug 2022 16:04:20 +0200 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. 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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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 :) Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
24.08.2022 15:35, Jiří Činčura wrote: I would unify the `pdb`, `debuginfo`, etc. into simple `debug` suffix. Agreed. Dmitry Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
I would unify the `pdb`, `debuginfo`, etc. into simple `debug` suffix. Probably Alex can clarify, but it really the ARM32/64 for Linux? And if so, do we even need ARM32? -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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. I'm also not sure about arm64 vs aarch64 differences. Here https://github.com/asfernandes/firebird/releases/tag/v4.0.0-aarch64-asfernandes I built a Linux RaspBerry pi and named aarch64 but never published it as official. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Improve release filenames
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? Mark -- Mark Rotteveel Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] Improve release filenames
Hi! This is our Firebird 4.0.2 released files: Firebird-4.0.2.2816-0-Win32-pdb.exe Firebird-4.0.2.2816-0-Win32-pdb.zip Firebird-4.0.2.2816-0-Win32.exe Firebird-4.0.2.2816-0-Win32.zip Firebird-4.0.2.2816-0-x64-pdb.exe Firebird-4.0.2.2816-0-x64-pdb.zip Firebird-4.0.2.2816-0-x64.exe Firebird-4.0.2.2816-0-x64.zip Firebird-4.0.2.2816-0.amd64.tar.gz Firebird-4.0.2.2816-0.arm.tar.gz Firebird-4.0.2.2816-0.arm64.tar.gz Firebird-4.0.2.2816-0.i686.tar.gz Firebird-4.0.2.2816-0.tar.xz Firebird-debuginfo-4.0.2.2816-0.amd64.tar.gz Firebird-debuginfo-4.0.2.2816-0.i686.tar.gz Firebird-withDebugInfo-4.0.2.2816-0.arm.tar.gz Firebird-withDebugInfo-4.0.2.2816-0.arm64.tar.gz (missing MacOS which would be: Firebird-4.0.2.2816-x86_64.pkg) 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-windows-x86-pdb.exe Firebird-5.0.0.2816-0-windows-x86-pdb.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-pdb.exe Firebird-5.0.0.2816-0-windows-x64-pdb.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-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 Firebird-5.0.0.2816-0-linux-x86.tar.gz Firebird-5.0.0.2816-0-linux-x86-debuginfo.tar.gz Firebird-5.0.0.2816-0-source.tar.xz Firebird-5.0.0.2816-0-macos-x64.pkg Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
