[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Handling directories of large files

From: <subversion_at_jelmail.com>
Date: 2007-11-07 12:51:23 CET

Hello, I'm after some "best practice" for handling directories of large
files.

I have a repository with a directory that contains tarballs of various
packages I use. This directory is huge. If I wish to add to this directory
I have to check out the entire directory, add files to the working copy and
check back in. Is there a better way to do this? Typically the files here
are added but never modified.

Similarly, I have a directory containing iso images. This directory also
contains build scripts that make the iso images using stuff I have
elsewhere in subversion. To change the build scripts I have to check out
the entire directory, make my changes to the build script working copy and
check back in. This can mean checking out gigabytes of data just so I can
change one line of script. Some files here need to be modified, but the
vast majority don't.

My repo looks like:

repo
    iso
        build_script
        readme
        iso_release1.iso
        iso_release2.iso
        iso_release3.iso
    packages
        package1.tar.gz
        package2.tar.gz
        package3.tar.gz
        package4.tar.gz
        ...

Perhaps I am doing this with an incorrect repository structure and I
misunderstand how svn should be used. Any help and guidance would be
greatly appreciated.

Many thanks,
John

--------------------------------------------------------------------
mail2web.com - Microsoft® Exchange solutions from a leading provider -
http://link.mail2web.com/Business/Exchange

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 7 12:51:47 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.