NEW! Subversion control and test for future Blender binaries.

Next to the release code, a subversion number is written in the file
now. This is in the chunk GLOB, which is now in beginning of file.

Subversions can be used to have finer control over do_versions(), so you
don't have to wait for a release to patch stuff nicely. We can also
increase these subversions regularly to denote important changes.
If a subversion is not 0, it's being printed in the header, so a user can
also verify the state. (We might even tag cvs for it?).

Next to this, a minimum version and subversion number are written too.
From now on, if you change files in a way a past binary cannot read this
nicely anymore, you should set these minima to the current version.
This was especially added for the new mesh layers, which will not work
for older binaries once we make 2.43.

1 files changed, 3 insertions, 1 deletions

diff --git a/source/blender/blenloader/intern/readfile.h b/source/blender/blenloader/intern/readfile.h
index fd7e5c0ee00..0a398bfce43 100644
--- a/source/blender/blenloader/intern/readfile.h
+++ b/source/blender/blenloader/intern/readfile.h
@@ -68,7 +68,8 @@ typedef struct FileData {
 	struct SDNA *memsdna;
 	char *compflags;
 	
-	int fileversion;
+	int fileversion, filesubversion;
+	int fileminversion, fileminsubversion;
 	
 	struct OldNewMap *datamap;
 	struct OldNewMap *globmap;
@@ -89,6 +90,7 @@ typedef struct BHeadN {
 	struct BHead bhead;
 } BHeadN;
 
+
 #define FD_FLAGS_SWITCH_ENDIAN             (1<<0)
 #define FD_FLAGS_FILE_POINTSIZE_IS_4       (1<<1)
 #define FD_FLAGS_POINTSIZE_DIFFERS         (1<<2)