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?
Have fun!
Daniel
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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 2 03:22:55 2006