Menu
▾
▴
firebird-devel
|
From: Mark R. <ma...@la...> - 2022-08-25 10:20:08
|
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 |
|
From: Adriano d. S. F. <adr...@gm...> - 2022-08-25 10:38:24
|
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 |
|
From: Dmitry Y. <fir...@ya...> - 2022-08-25 10:34:42
|
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 |
|
From: Dimitry S. <sd...@ib...> - 2022-08-25 10:38:35
|
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. |
|
From: Adriano d. S. F. <adr...@gm...> - 2022-08-25 10:55:27
|
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 |
|
From: Mark R. <ma...@la...> - 2022-08-25 11:01:35
|
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 |
|
From: Stefan H. <li...@st...> - 2022-08-25 13:27:10
|
> 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 |
|
From: Mark R. <ma...@la...> - 2022-08-25 16:16:20
|
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-<version>-<os-family>-<target-cpu>[-qualifier]. I don't see the need, nor the point to deviate from this for Windows. Mark -- Mark Rotteveel |
|
From: Gabor B. <mln...@bg...> - 2022-08-25 13:49:33
|
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 |
|
From: Jiří Č. <ji...@ci...> - 2022-08-25 13:53:31
|
> 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/ |
|
From: Stefan H. <li...@st...> - 2022-08-25 14:34:14
|
>> > 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 |
|
From: Jiří Č. <ji...@ci...> - 2022-08-25 17:11:41
|
> 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/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X