Could you, dear gods ... OTTD developers, also release the source code of a new binary release as a tar.gz or tar.bz2 (much better than zip) or something, please?
Saskia wrote:Could you, dear gods ... OTTD developers, also release the source code of a new binary release as a tar.gz or tar.bz2 (much better than zip) or something, please?
Why not get the newest version from svn?
TrueLight:"Did you bother to read any of the replies, or you just pressed 'Reply' and started typing?" <@[R-Dk]FoRbiDDeN> "HELP, this litte arrow thing keeps following my mouse, and I can't make it go away."
Because I (and probably maaaany others) then had to fight with the checkout procedure every new release. I even don't have a SVN client ... and nearly every open source project has an stable code package, why not OTTD? It would be much more comfortable to download
Does SVN transfer the source compressed? I only have a modem - the uncompressed source is about 12 MB! And where's the problem, if Ludde even releases a compiled binary, to release a source package ...
Saskia wrote:Does SVN transfer the source compressed? I only have a modem - the uncompressed source is about 12 MB! And where's the problem, if Ludde even releases a compiled binary, to release a source package ...
That would be 29 minutes with 7 k/s (max for 56 k modem)
In theory you only have to do this once because svn only transfers modified files.
oTTD uncompressed is only about 5 megs. Excluding of course all compiled files, and needed TTDLX graphics.
Since most of this is text, it will be max 3 megs orso. Could be easily downloaded, even on a dialup
TrueLight:"Did you bother to read any of the replies, or you just pressed 'Reply' and started typing?" <@[R-Dk]FoRbiDDeN> "HELP, this litte arrow thing keeps following my mouse, and I can't make it go away."
Could be cause the 'Makefile' is set to debug mode automatically, not to release mode. Anyway, it's still huge
I don't care anyway, the conn is fast enoughl