On Jan 5, 2005, at 7:28 PM, Branko Čibej wrote:
> Ben Collins-Sussman wrote:
>
>> I'm trying to be a helpful citizen and build/upload a 1.1.2 win32
>> .zip for public consumption.
>>
>> I'm having no problems building the 1.1.2 tag, but I just noticed
>> that branko's 1.1.2 zipfile contains a whole extra 'share\locale\'
>> folder full of .mo message translations.
>> I've never distributed these before, and it seems like a good idea.
>>
>> (gettext is already required to build in win32: we distribute
>> libiconv and libintl, and all the iconv locales in our zipfile. I
>> guess it makes sense to distribute .mo message translations too.)
>>
>> Looking through our INSTALL file, I see nothing in the win32 build
>> instructions that explains how to use win32 gettext tools to compile
>> the .po files. Can someone explain? Shouldn't we augment INSTALL?
>
>
> Yes, yes, yes and yes. Hm. I lost count there.
>
> Anyway, I cheat by explicitly building the "locale" project, which
> converts the .po files into .mo files, then use a slightly modified
> version of build/win32/make_dist.py to generate the package.
>
> Yes, "locale" shoudl probably become a dependency of __ALL__.
>
I have another problem, brane. :-)
On the users@ list, I've been getting reports that my 1.1.2 .zip
includes a version of libintl that breaks existing 1.1.1 mod_dav_svn
installations. Apparently your 1.1.1 zip included libintl 0.14, and I
included 0.12? Or something like that.
In any case, I'm confused as to why it should matter at all. I've been
using the same win32 gettext-0.12 package for the last 8 months with no
problems. Why would it suddenly jump up and bite people? And is there
any way the win32 build system can check that gettext is a certain
minimum version?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 6 03:13:43 2005