Hi, It's nice to have a list to discuss things, thanks Fridrich! Applications needing gettext for localisation only need libintl. That library is currently included in gettext-runtime. In that package however, there are also some other large (> 1MB) libraries and some dependencies (libg++, etc.) that are not needed for minimal runtime support. Is it OK to submit a request for separating libintl in its own package? Maarten -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-mingw+help@opensuse.org
Yeah, in my opinion, more we split the packages better it is so that when someone constructs an installer, the rpm dependency tracking installs only the needed libraries. I would check how different Linuces split this and would inspire myself from they naming; if that one does not exist, I would prefer mingw32-libintl for that library. Please, when you are doing this for the 32-bit windows builds, clone the change also into the 64-bit repositories. Cheers Fridrich On 03/03/2011 17:10, Maarten Bosmans wrote:
Hi,
It's nice to have a list to discuss things, thanks Fridrich!
Applications needing gettext for localisation only need libintl. That library is currently included in gettext-runtime. In that package however, there are also some other large (> 1MB) libraries and some dependencies (libg++, etc.) that are not needed for minimal runtime support.
Is it OK to submit a request for separating libintl in its own package?
Maarten -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-mingw+help@opensuse.org
2011/3/3 Fridrich Strba
Yeah, in my opinion, more we split the packages better it is so that when someone constructs an installer, the rpm dependency tracking installs only the needed libraries.
Yes, this is exactly how I got to the issue. I have a python script that downloads a package and its dependencies and repackage it in a ready-to-go zipfile. It included to many files for gettext.
I would check how different Linuces split this and would inspire myself from they naming; if that one does not exist, I would prefer mingw32-libintl for that library. Please, when you are doing this for the 32-bit windows builds, clone the change also into the 64-bit repositories.
I went for mingw32-libintl. How do I clone the change for 64bit? And a related question: is the difference between mingw32 and mingw64 just the target Windows version, or are there more differences?
Cheers
Fridrich
Maarten -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-mingw+help@opensuse.org
Hello, On 03/03/11 20:39, Maarten Bosmans wrote:
Yes, this is exactly how I got to the issue. I have a python script that downloads a package and its dependencies and repackage it in a ready-to-go zipfile. It included to many files for gettext.
Nice work, would be interesting to see that. There is a promise that once OBS will be able to spit ZIP files too, so this would maybe be useful to put to the mingw{32,64}-filesystem infrastructure packages, just for the case one would automatize this one day.
I went for mingw32-libintl.
I accepted it as you could see :) And I cloned it for 64-bit windows.
How do I clone the change for 64bit? And a related question: is the difference between mingw32 and mingw64 just the target Windows version, or are there more differences?
Yup, basically they are the same packages for different windows target. The porting strategy I have (and as I can see from the resulting packages, Tor Lillqvist, the guru of all of us that precedes us and follows us and is in us, is doing it too :)) is to keep the possibility to build both stuff from the same sources. That means, if a patch is needed, it is good to have the parts of code that differ properly #ifdef-ed and the resulting patch applied in both the mingw32 and mingw64 projects. For the time being, my synchronization strategy is to copy all files that dont contain mingw32 in the name over and for the rest, to do this one-liner "for i in mingw32*; do cat $i | sed 's#mingw32#mingw64#g' | sed 's#MINGW32#MINGW64#g' >`echo $i | sed 's#mingw32#mingw64#g'`; done". Note that this is not possible with the mingw32-filesystem package which does not rely on the macros it installs itself. Gosh, I start to be too verbose again. Let me stop here and wait for questions if any. Cheers F. -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-mingw+help@opensuse.org
participants (2)
-
Fridrich Strba
-
Maarten Bosmans