Hi,
Is it your checked out repository which increases in size when you
tag stuff, or is it your actual repo' on the server?
Like the guy said before, a tag is just a snapshot of a revision -
it should not exist in full unless you get it out of the repository -
but I may be wrong...
Also, you can "ignore" directories and files from the versioning
http://svnbook.red-bean.com/en/1.5/svn.advanced.props.special.ignore.html
Using TortoiseSVN, you can right click, look at the properties for
the file / folder and add a "New" one - "ignore" is in the drop down
list - this can be a bit fiddly for folders - I think I had to do this
with a freshly checked out repo' before it stopped moaning at me.
Ignoring does not solve your "filtering out" tags problem - it looks
like people asked for this a while ago, but it has not been implemented.
http://www.google.co.uk/search?hl=en&q=svn+checkout+filtering&btnG=Search&meta=
<http://www.google.co.uk/search?hl=en&q=svn+checkout+filtering&btnG=Search&meta=>
You can checkout various parts of a repository into the same
directory, but I understand that this could be a pain if you have to
root around and find the place to start.
HTH
Glen
Hans Wichman wrote:
Hi,
yep using subversion.
I usually create the tag in my workingcopy, but on the server would be fine
as well.
We have one system though with some 500 small projects, all in a single
repository, which are tagged before they are released.
But the structure for that repository is like:
project1\tags
project1\trunk
project2\tags
project2\trunk
Some contentdevelopers have to work on a number of those small projects, so
they just check out the root of the repository :).
Would be nice if you could say something like "get this directory and all
subdirectories but ignore the tags" or something like that.
Another issue though is that binary assets often completely change after
updating (eg an flv thats rerendered), so the whole file is submitted to svn
again (since about every byte differs). Not sure what I'm looking for here,
something like being able to put a file in a repository, without tracking
it's history I guess (since it's content are derived from other material
which is leading).
regards,
JC
On Wed, Dec 10, 2008 at 5:59 PM, Ian Thomas <[EMAIL PROTECTED]> wrote:
Don't know how you've got your server setup, or which version control
system you are using...
We are using SVN. If you create a tag, it just creates an alias to the
files, not a true copy; so the size in the repository doesn't go up by
a huge amount.
Are you keeping a local copy of all your tagged code or something?
Ian
On Wed, Dec 10, 2008 at 2:36 PM, Hans Wichman
<[EMAIL PROTECTED]> 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
--
Glen Pike
01326 218440
www.glenpike.co.uk <http://www.glenpike.co.uk>
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
