On 30 July 2011 17:25, Jacob Nevins
<0jacobnk.fc...@chiark.greenend.org.uk> wrote:
>> btw. I plan to make only builds like these (freeciv in one zip) in
>> the future. As you are the only one who has ever successfully used
>> these builds, would you mind writing short instructions how you setup
>>
>>> Did this build also contain the uncommitted patch for bug #18396 (the
>>> bzip2 one, file #13687)?
>>
>> No, I considered having them both patches in that build, but thought
>> that you probably want to test effects of single patch without
>> worrying what the other patch does to results. I ca
On 30 July 2011 17:06, Marko Lindqvist wrote:
> On 30 July 2011 16:53, Jacob Nevins
> <0jacobnk.fc...@chiark.greenend.org.uk> wrote:
>> Marko Lindqvist writes:
>>> On 29 July 2011 02:30, Jacob Nevins
>>> wrote:
Attached patch makes secfile reading treat \r\n and \n\r line endings the
s
On 30 July 2011 16:53, Jacob Nevins
<0jacobnk.fc...@chiark.greenend.org.uk> wrote:
> Marko Lindqvist writes:
>> On 29 July 2011 02:30, Jacob Nevins wrote:
>>> Attached patch makes secfile reading treat \r\n and \n\r line endings the
>>> same as \n, if it sees them (e.g., if opening a file with DOS
Marko Lindqvist writes:
> On 29 July 2011 02:30, Jacob Nevins wrote:
>> Attached patch makes secfile reading treat \r\n and \n\r line endings the
>> same as \n, if it sees them (e.g., if opening a file with DOS/Windows line
>> endings on Unix).
>
> I don't know if there's anything in this patch
On 29 July 2011 02:30, Jacob Nevins wrote:
>
> Attached patch makes secfile reading treat \r\n and \n\r line endings the
> same as \n, if it sees them (e.g., if opening a file with DOS/Windows line
> endings on Unix).
>
> Tested on Unix. I haven't checked what happens with a Windows build of
> Fre