commitinfor and cvswrapper

[Matthew Ogilvie]

Our CVS server is running on Linux and users use CVS.exe or WinCVS on
Windows client machines. Is there any way to block users from adding or
committing certain files or file patterns to our CVS repository?

Depending on exactly which client(s) your users use (and how), it might
help significantly to simply include a line like "[Tt]humbs.db" (without
the quotes) in the directory's committed ".cvsignore" file. Some
GUI clients (like wincvs) will automatically exclude ignored files
from file listings in at least some modes, making them much harder
to add by accident.

Limitations:
- Does not help if your users are doing "cvs add *".
- Does not help much if your users are regularly creating new
image directories, which each need their own .cvsignore
file. You might be able to use the repository-wide
CVSROOT/cvsignore file instead, but it wouldn't surprise me
if most GUI clients don't know how to check it when doing
file listings (not sure).

--
Matthew Ogilvie [***@mailcan.com]

[Rez P]

Thanks Mathew. That's what I exactly found out: That when users create new image subdirectories, the thumbs.db files get created and unintentionally or rather carelessly get checked in. It'll be really cumbersome to remember to traverse through each subfolder to edit .cvsignore files locally or remind each new employee/developer to turn off their Window's image cache. At least in XP you could access and turn it off through Explorer's options but in Vista this option is hidden and not easily and intuitively accessible or available and you either have to know how to hack the Registry or run gpedit.msc.

I did checkout, modify, and add *humbs.db to my CVSROOT/cvsignore file on the server but somehow it wasn't working and users were still checking in those files. So thanks to Larry's help, the script he sent me, was put in place and works perfectly now.

Thanks

Rez

Date: Thu, 17 Dec 2009 01:27:14 -0700
Subject: Re: commitinfor and cvswrapper

Our CVS server is running on Linux and users use CVS.exe or WinCVS on
Windows client machines. Is there any way to block users from adding or
committing certain files or file patterns to our CVS repository?

Depending on exactly which client(s) your users use (and how), it might
help significantly to simply include a line like "[Tt]humbs.db" (without
the quotes) in the directory's committed ".cvsignore" file. Some
GUI clients (like wincvs) will automatically exclude ignored files
from file listings in at least some modes, making them much harder
to add by accident.
- Does not help if your users are doing "cvs add *".
- Does not help much if your users are regularly creating new
image directories, which each need their own .cvsignore
file. You might be able to use the repository-wide
CVSROOT/cvsignore file instead, but it wouldn't surprise me
if most GUI clients don't know how to check it when doing
file listings (not sure).
--

_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141664/direct/01/