Please reply to the list and not to me directly.
On 5/21/07, Kevin Grover <kevin@kevingrover.net> wrote:
>
>
> On 5/21/07, Larry Martell <larry.martell@gmail.com> wrote:
> > We have a situation where we need to keep a template version of
> > a file under SVN control, and allow users to checkout this template
> > into their working copy. We want them to be able to modify this
> > file in their working copy, but we do not want them to be able to
> > check their changes to this file back in. Is there any way to
> > achieve this with SVN? (We can't set svn:needs-lock and then
> > lock the file because then it gets checked out read-only).
> >
> > Thanks!
> > -larry
> >
>
> The normal way of doing this is to check in a template file and instruct
> users to copy that to the actual name when they check out for the first
> time, then ignore that name.
>
> Example
> .../svn/repo/conf/myapp.conf.tmpl
> .../svn/repo/conf[svn:ignore contains 'myapp.conf']
>
> When they first check it out, they manually copy the myapp.conf.tmpl to
> myapp.conf and modify it all they want. Since it's ignored, it will not be
> included on check-ins**
>
> ** It can still be checked in/committed if explicitly asked for (on the
> command line for example). You could prevent this with hook scripts.
If I could get the users to follow directions this would work, but
unfortunately they don't, so this needs to be an automatic solution.
-larry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 22 14:33:49 2007