Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Gabriel Genellina wrote: > At Friday 15/9/2006 14:11, Rick Martin wrote: > >> This maybe slightly OT but I'd like to see how others deal with this >> issue. >> I have a development system under CVSNT control. There are a handful of >> configuration type files that each user needs, but once the user gets the >> default version of the files I do not want them to receive any more. >> After >> the first check out I want these files to be modifiable by the user >> and do >> not want them to commit or update them. Is there any way to indicate a >> file >> in CVS that is only updated on Check out vs. Update? > > > We use a setup script which: > - creates directories > - checks the needed modules out, plus a "template" module > - uses the "template" to actually build the config files > - puts the config files in .cvsignore You might want to look at the substitution mode "s" as well. http://www.cvsnt.org/manual/html/Substitution-modes.html >>>> s File is never considered modified on the client. A normal commit will never commit this file, unless -f is used to force it. Use with care, and for files that change infrequently, since local changes will be lost on update. <<<< Not sure if that's what your or the OP is looking for, but it might be useful (e.g. just make the 'templates' have the same name as your config files and you're set to modify them as needed directly). That doesn't apply to the OP's update side though, I would guess the updates might be merged into the file if there's a new version of the 'template' released, but it's something to look at. Regards, -- Glen Starrett