Process Recommendation Request

[Rob Wilkerson <r....@gmail.com>]

Has anyone found an effective method of switching between svn branches
when there are unversioned files and/or directories present?

I have an application that, in several locations within the code base,
generates files and directories at runtime.  For containment, these
are kept within the install root which means within the working copy
code base.  This seems to be causing real problems when switching,
however.  Is there a good way to do this?

One note: these files, once generated are not ignored (svn:ignore).
They are simply unversioned.  I'm not entirely sure that I understand
all of the ramifications of setting this property (which probably
means I definitely do not), but from what I can tell (and please
correct me if I'm wrong), setting svn:ignore seems to have some impact
on the repository and I'd rather the repository have absolutely no
idea that these files and directories exist.

Any thoughts would be appreciated.  Thanks.

-- 

Rob Wilkerson

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Process Recommendation Request

[William Nagel <bi...@stagelogic.com>]

On Oct 5, 2006, at 7:28 AM, Rob Wilkerson wrote:

> Has anyone found an effective method of switching between svn branches
> when there are unversioned files and/or directories present?
>
> I have an application that, in several locations within the code base,
> generates files and directories at runtime.  For containment, these
> are kept within the install root which means within the working copy
> code base.  This seems to be causing real problems when switching,
> however.  Is there a good way to do this?

If the files are automatically generated, would it make sense to  
delete them prior to doing the switch?  You could write a script that  
would do the deletion and the switch in one swipe.

>
> One note: these files, once generated are not ignored (svn:ignore).
> They are simply unversioned.  I'm not entirely sure that I understand
> all of the ramifications of setting this property (which probably
> means I definitely do not), but from what I can tell (and please
> correct me if I'm wrong), setting svn:ignore seems to have some impact
> on the repository and I'd rather the repository have absolutely no
> idea that these files and directories exist.

The repository would continue to have no idea that the files exist,  
but it would know that the files -could- exist (or if you can put it  
into the svn:ignore with wildcards that a file matching a certain  
pattern might exist).

-Bill

>
> Any thoughts would be appreciated.  Thanks.
>
> -- 
>
> Rob Wilkerson
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org