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

Re: checkout-only files with svn - How?

From: Ryan Schmidt <subversion-2006q2_at_ryandesign.com>
Date: 2006-06-02 11:47:17 CEST

On Jun 2, 2006, at 03:21, Daniel Lohmann wrote:

> Ryan Schmidt schrieb:
>> On Jun 1, 2006, at 05:51, Daniel Lohmann wrote:
>>> I have a set of files (user configuration files) that are
>>> required to build the project, but are modified per-user on the
>>> users side.
>>> Hence, I want these files to be checked out / updated only if
>>> they do not exist. Morover, changes to them should never be
>>> committed into the repository.
>>> I experimented with svn:ignores, however, svn refuses to check
>>> out ignored files on the first checkout :-)
>> http://subversion.tigris.org/faq.html#ignore-commit
> Thanks Ryan!
> >>> FAQ >>>
>> I have a file in my project that every developer must change, but
>> I don't want those local mods to ever be committed. How can I make
>> 'svn commit' ignore the file?
>> The answer is: don't put that file under version control. Instead,
>> put a template of the file under version control, something like
>> "file.tmpl".
>> Then, after the initial 'svn checkout', have your users (or your
>> build system) do a normal OS copy of the template to the proper
>> filename, and have users customize the copy. [...]
> <<< FAQ <<<
> This is, however, exactly what I don't want my users to have to
> do :-( The files are actually the project files of the build
> environment, so I can't let the build system do the template copy
> (as it would not start without them). And extra run-me-after-first-
> checkout-scripts would be kind of tedious, as they had to be
> developed for many different platforms.
> I understand that I am currently lost here. However, are there any
> plans to add a feature such as a "svn:checkout-only" property to svn?

Unfortunately, I'm not aware of any such plans.

I haven't had to use this technique myself yet, but it sounds like
something you'd only have to do right after you check out a working
copy, which is not something you're supposed to have to do that
often, hence it's not supposed to be so inconvenient to manually
rename a few files before getting to work. Are you creating new
working copies very often? If so, why? Or are there a very large
number of files that are having to be renamed in this way?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 2 11:49:11 2006

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.