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

RE: Keeping a file under SVN control but preventing it to update locally

From: Bob Archer <bob.archer_at_amsi.com>
Date: Wed, 1 Jul 2009 10:32:57 -0400

> Hi, I hope this is the place to post this, if not, sorry!
>
> What I want is the tipical configuration file, that must be under SVN
> control so I get it when Checking out a repository.
> But what I get is more a template than a real config file.
> Then I have to fill it with my local configuration.
>
> I've seen the approach of naming the file something like
> "config.ini.template" in the SVN repository, but the actual config file
> should be renamed to config.ini
>
> The thing is whoever created the repository didn't name it that way,
> so,
> what I want is this:
> Marking the file in TortoiseSVN in a way that it doesn't get updated
> when I update its folder, but the file doesn't get deleted on the
> repository.
> In other terms, can I mark a file so it's downloaded on only Checkout
> but never on updates?
> And it also should be out of any commit.

Just rename the file in your repo adding the .template extension and notify your devs they will have to copy it to the file without the .template extension and edit for their local env. Also, add an ignore for the real file name so no one will accidentally add it.

BOb

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2367056

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-07-01 16:33:24 CEST

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

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