On Sunday, 5 October 2008 at 1:50, bugs buggy wrote: > With the upcoming release of the FMV patch in trunk, *before* we add the > fmvs into the repo, I would like to confirm the data structure.
Question: Why do you want to add those to SVN? I can understand the rest of the data (well, perhaps not the music, but that is not that large), but the FVMs? Those are large, won't really be modified and are not necessary for the game. > trunk/data (only pumpkin official stuff, + derivatives of their work?) > trunk/code or trunk/source > trunk/FMVs (since it is optional?) And even separated from the rest? What's the difference to just having a separate archive then? And when you don't have the movies in SVN, what exactly are the benefits of separating source and data? Packaging? Were there any complaints about that? The Debian packaging system easily allows the creation of separate packages from one source archive, and I'd imagine any other deserving that name does as well. Redownloading changed textures? How often are those changed? I think Buginator complained about the bandwidth required comparing revisions before and after a big change. But if the src and data are separated, that won't magically make those old big changes go away, and introduce another one. And this problem seems easier solved by having the complete SVN history locally, with a tool like git-svn, hgsvn (for Mercurial) or SVK (I guess there are more, those are just the ones I know of). Those were the reasons listed in this thread, and both don't seem very convincing to me. Are there other advantages I have missed? _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
