How would you use a Distributed Version Control System like Mercurial or Bazaar to manage large binary files? -
specifically situation i'm thinking of have large asset .psd 200 mb. artist goes , changes few pixels , checks in. assuming deltas not kept thats 200 mbs updates clone/branch have history off. given full development cycle lot of information pull each client.
what ability mark files these "keep history on server", traditional centralized vcss svn or perforce. may lose benefits of dvcs these files willing accept long can use 1 vcs (as opposed 1 assets , 1 code).
any suggestions on how (if possible) appreciated.
for mercurial, can use bfiles extension (or 1 of others listed on page). file metadata stored inside repo, , content of big files kept on central server. haven't used of extensions, though, can't tell 1 best choice.
Comments
Post a Comment