Hi list, In order to understand the differences between mingw32 and mingw64 packages, I made a diff between all the packages in the two projects. To be able to compare the two, a script was used to rename all directories/files with mingw32 or mingw64 in the name to mingwXX and do the same replacement for contents of .spec files. There are several types of differences between win32 and win64 projects: Unintentional whitespace differences or added empty lines, e.g. --- windows:mingw:win32/mingwXX-freetype/mingwXX-freetype.spec 2011-04-13 16:54:02.444618000 +0200 +++ windows:mingw:win64/mingwXX-freetype/mingwXX-freetype.spec 2011-04-13 16:53:57.968618000 +0200 @@ -14,7 +14,7 @@ -Source1: http://download.savannah.gnu.org/releases/freetype/freetype-doc-%{version}.tar.bz2 +Source1: http://download.savannah.gnu.org/releases/freetype/freetype-doc-%{version}.tar.bz2 Unsynchronized versions, e.g. --- windows:mingw:win32/mingwXX-gc/mingwXX-gc.spec 2011-04-13 16:54:02.456618000 +0200 +++ windows:mingw:win64/mingwXX-gc/mingwXX-gc.spec 2011-04-13 16:53:57.980618000 +0200 -Version: 7.1 +Version: 7.2alpha4 (with corresponding different .tar.gz files) Differences I'm unable to tell whether they are intentional or unintenional, e.g. --- windows:mingw:win32/mingwXX-gcc/mingwXX-cross-gcc.spec 2011-04-13 16:54:02.464618000 +0200 +++ windows:mingw:win64/mingwXX-gcc/mingwXX-cross-gcc.spec 2011-04-13 16:53:57.992618000 +0200 -%define include_java 1 +%define include_java 0 Real differences in packaging that are correct, e.g. --- windows:mingw:win32/mingwXX-glib2/mingwXX-glib2.spec 2011-04-13 16:54:02.556618000 +0200 +++ windows:mingw:win64/mingwXX-glib2/mingwXX-glib2.spec 2011-04-13 16:53:58.084618000 +0200 -%{_mingwXX_bindir}/gspawn-win32-helper.exe +%{_mingwXX_bindir}/gspawn-win64-helper.exe Is there some (semi-)automated way to keep the packages in both repositories synchronized? That would prevent a lot of these little mistakes. (In general I'm quite unaware of what the workflow is to get both win32 and win64 packages. I only submit mingw32 requests and let Fridrich handle the rest.) A possible (but quite intrusive) solution could be to rename all the packages to just a mingw- prefix (without numbers) and do the same for the rpm macros. That way all the packages in win64 could be branched of the win32 packages. For most packages this would just work and packages that need specific changes, those can be added to the mingw64 package. Maarten -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-mingw+help@opensuse.org