On 11/18/06, Jonathan Wallace <jonathan.wallace@gmail.com> wrote:
> I'm looking to see if there is a built in feature in subversion 1.4 that is
> similar to the link posted by Mark (though I note the proposal explicitly
> states 'svn status' has yet to be investigated).
>
> The feature that I seek allows one to mark a set of versioned files so that
> they are ignored when committing, updating and statusing. The idea being
> that individual developers on different machines need to configure the files
> differently due to their respective environments but the build version of
> the files needs to be kept a certain way for the ultimate deployment.
>
> I keep getting drawn to svn propset svn:ignore but it doesn't seem to work
> in my tests though I may be doing something wrong. Can anyone please point
> me in proper direction if there is something that I've missed in the
> subversion book?
There is no feature like that in Subversion.
The recommendations I have seen are to create a template file that
your developers copy and customize and that your build/deploy just
copies. Then the template file is versioned, and the "real" file is
not versioned (and added to svn:ignore so that it does not become
versioned).
It does not work for every scenario, but it can work.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 18 23:09:36 2006