Smaller projects we've done what you have. My understanding of SVN
theory would indicate that making a tag shouldn't increase the size
of your repository because a tag is just pointers to a version of a
file, the file is not duplicated.
Adding or changing assets does of course increase the size of the
repository because they are added as binary files and not differenced
like text (code) files.
For bigger projects, you might be better off going with a whole
separate asset management system. This keeps your code repository
small, easy to backup, etc. and allows you to use a better tool for
asset management.
I also add a "resources" folder if necessary. This contains anything
else such as fonts that you might need to create a build with the
theory you can download everything from the trunk with maybe only
adding assets to create a working build on any computer.
On Dec 10, 2008, at 9:36 AM, Hans Wichman wrote:
Hi list,
I was wondering how you handle your assets in version control.
I usually follow a standard project setup something like:
trunk
branches
tags
The trunk contains for example sources, deploy, deploy/assets
Now especially the assets folder tends to get very large.
Each time I tag the trunk, the size multiplies.
I was wondering how others are handling this, and looking for a
better way
to handle the assets.
Not sure if there is a quick solution to this though:)
regards,
JC
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
