Re: use case for config files in repository

> >I have a question regarding configuration files in a repository.
> >Assume that I have a configuration file just as log4j.properties or
> >some database connection configuration file. Now, this file needs
> >to be in the repository because it is relevant to the project, but
> >certain fields in the file change, like username and/or password or
> >perhaps logfile location based on the computer on which the program
> >is running. After I checkout a version of the repository onto a
> >computer, would there anyway to tell subversion that I no longer
> >want to consider this file when updating or committing?
> >
> >
>
> No, you can't do that, but you can do something else: Check in a
> template for that file under a different name, for example,
> "log4j.properties.template", and require people to copy it to
> "log4j.properties" and customize that. You can tell Subversion to ignore
> that file.

Of course! .dist files. Duh

Dan

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Daniel Allen, <dan@mojavelinux.com>
http://www.mojavelinux.com/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Real programmers just hate to get up in the morning, and 
contrary to Ordinary People, they're in better shape as 
it gets closer to nighttime.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org