In the internal CR repository, there is "source", "docs", "planet", "tools" and some other stuff. "planet" contains the game data and is presumably named after Clonk Planet. Do we want to keep that name in the name of tradition, or use something boring and obvious instead? (I'm against a nonobvious new name because an obvious name has obvious advantages.)
I think the one who creates the git/svn repository should decide this. And I guess this will be you anyway :P
Yes. But I don't want to spent time thinking about it. Hence this topic: If somebody comes up with a good name or a good reason for one, I can just use that.
It would probably contain the executable as well, so I would call it game. If someone checks out the game from the repository, he would probably search for the folder containing the game to start, which should be easy to find.
No, executables shouldn't be in the repository. We shouldn't force everyone to download megabytes of unnecessary data.
since my problems with configure i would suggest to contain executables, too.
There's a difference between not putting big binaries into the repository and not distributing them at all, you know.
In the future, perhaps some kind of Continous Integration System/Server (e.g. like CruiseControl) could be nice to have for doing and distributing nightly builds, perhaps also running automated regression tests, etc.
But it's certainly some work to set this up for all the supported platforms...
But it's certainly some work to set this up for all the supported platforms...
ACK, also I agree that more or less recent executables should be in the game repository. In the worst case, it's just some megabytes of unnecessary data but eases "nightly builds" a lot.
No, they shouldn't. Binaries don't diff well, so every build would be contained in the repository in nearly full size, which would amount to a lot of space. I don't know what nightly builds have to do with it, though.
What's the problem with putting them somewhere else? We don't need to keep every binary in the repository forever.
It should be easier for people who just do scripting but can't compile an engine. I.e., probably most of the Windows/Mac developers.
There's still the possibility to store the binaries somewhere external to the repository. I actually don't know of any project that has executable binaries in its repository.
They won't need to compile an engine, just get the engine from a public FTP instead of the repository... We could provide a script to do that if we want that kind of convenience.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill