Yes, but apart from that solution, is there a better way? I'd prefer not
having to tell the users to rename the file - it would be nice if they could
directly edit the configuration file.
On 3/14/07, Les Mikesell <lesmikesell@gmail.com> wrote:
>
> Andrew Close wrote:
> >> On 3/14/07, Andrew Close < aclose@gmail.com> wrote:
> >> > On 3/14/07, Jean-Noël Rivasseau < elvanor2007@gmail.com> wrote:
> >> > > Hello
> >> > >
> >> > > My problem is this one: I would like to have a configuration file
> >> in my
> >> > > subversion project, along with the code. Ideally, developpers
> >> checking
> >> out
> >> > > my project via SVN would get a copy of a (default) configuration
> >> file.
> >> Thus
> >> > > they would know that this file is there and needs to be modified
> >> > > accordingly.
> >> > >
> >> > > However I of course don't need the changes they make to the file
> >> to be
> >> > > commited to the SVN repository... since these changes reflect their
> >> (local)
> >> > > configuration...
> >> > >
> >> > > Is there a way to have such a file in an SVN repository? svn status
> >> would
> >> > > not show this file (as if it were ignored), but it would still be
> >> in the
> >> > > subversion repository.
> >> > >
> >> > > If someone can help me (I hope I've been clear enough), thanks in
> >> advance.
> >> > >
> >> >
> >> > i know you can do what you have stated, but i don't have the solution
> >> > for you. :)
> >> > i'm pretty sure you can specify that certain files are not to be
> >> > updated to the repository or that they can't be re-committed. so a
> >> > developer would be able to check out the config file, modify it for
> >> > their own needs, and when they accidentally attempt to commit their
> >> > changes to the repository that particular file is ignored.
> >> > you could also write a pre-commit hook script that looks for that
> >> > particular file and disallows check-in...
> >> >
> >
> > On 3/14/07, Jean-Noël Rivasseau <elvanor2007@gmail.com> wrote:
> >> Ok thanks anyway (it's good to know it CAN be done), but now does
> someone
> >> have a simple solution? :)
> >>
> >> Jean-Noël
> >
> > Jean-Noel,
> >
> > when i replied to you i didn't reply to all.
> > hopefully someone else will have a 'solution' for you.
>
> The simple solution is to rename the example file so it can be under
> version control but won't be changed often, and provide instructions to
> copy the example to the expected file name before making local changes.
>
> --
> Les Mikesell
> lesmikesell@gmail.com
>
>
>
Received on Wed Mar 14 16:03:12 2007