Re: Newbie question: commit

[Spiro Trikaliotis]

Hello,

* On Sun, Apr 18, 2004 at 02:40:03AM -0300 address@hidden wrote:
 
>     The problem i'm facing is that custom_config.php file contains generic
> config values that needs to be modified by every developer/user to get the
> software working, but I don't want that nobody updates the repository with a
> custom user/passwd pair, for example, inside custom_config.php when doing a
> commit. So I suppose that if any developer that issues a commit, tries to go
> through it on a file by file basis, everything would go ok but what about a
> commit with cvs recursive behavior?

Another suggestion than the ones you got until now is the following:
Don't store custom_config.php into the repository but a "generator" (or
a template) for custom_config.php, which could be named something like
custom_config.php.generate. This way, custom_config.php will never the
checked in unless someone specifically ask for. You might want to add
custom_config.php into .cvsignore, but that's another matter.

Best regards,
   Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/