On Sun, Mar 2, 2014 at 12:39 AM, Alberto Torres <[email protected]> wrote: > How about this? > > Make Blender aware of repositories (e.g. checking .git exists in any of the > parents) so it can have repo-relative paths (defaulting to something like > //../repo-name/ for older blender versions) , and to make lists of > dependencies. When you open a .blend you can check which dependencies are > met, instead of dealing with individual missing files. > > Also it can have an ignore list, e.g. for reference images not needed > outside the author's machine.
Having to specifically support each version control system would IMHO be a mistake, we can just setup some way for Blender to define a project and the related files can be committed into version control along with the blend files, but don't think its really needed to set out exactly how this works just now unless someone plans to work on it soon. _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
