Re: Migrating to a new repository

Laker Netman wrote:
> >
> Well, it boils down to our business process. When the Art Dept finishes their portion of a project I get their files as hi-res TIFs. I do some final editing, convert the files into one of several different final formats and place those files into the repository. I don't want the TIFs committed, because A) the Art Dept may change something that might or might not affect me, B) I can always re-edit the TIFs I have to create a different final output for my piece and C) I don't want the repo "bloat" caused by committing TIF after TIF. I usually keep the TIFs for a few weeks or months, then just delete them. The same goes for Flash (video) files, and some others that aren't quite so space intensive.

Wouldn't it be simpler to just keep the TIFs outside of your svn working
directory in the first place and either teach your tools where to find
them or script moving the parts you do want committed into the working
copy and adding/committing them? Or if you are on an OS that
understands symlinks you might use a symlink to the tif in a different
location.

> I was thinking on the import side. I'll give it a try and see. Create an empty repo, set svn:ignore and import a directory tree. Based on the docs, I believe the import should honor the svn:ignore on files in the imported subfolders (which will be obvious, if true), but I want to see if the svn:ignore is automatically set on the subfolders as well. If not I'll script something to do it.

Depending on how much you already have committed, you might just 'svn
delete' the existing .tif's so they stop showing up in the head view and
stop adding them.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org