On Wednesday, February 23, Pavel Roskin wrote:
> 
> But if everybody works on the same project, why should they maintain
> separate .cvsrc ?

Because it's a personal configuration file.


> IMO personal configuration files are needed only for those who have
> personal preferences. People who have no preferences should use defaults.
> But the defaults may be different for different sites/repositories.

I believe that different sites/repos can have different proceedures, and
different conventions.  A .cvsrc file may help in reducing typing and may
ease the use of CVS within this environment, however, it is still a personal
thing to configure.


> > Then again, I would not be surprised if the same people are the ones
> > that think they need locking, when they do not.
> 
> Exactly! But I want to make CVS work better for them. Especially
> forgetting "-d" after "cvs update" is a major hassle because they cannot
> compile the project, then they run "su" and grab the code from my home
> directory (or even compile it there!), and then they complain that my code
> doesn't work for them.

The difference is that you'd rather perpetuate the ignorance of the CVS
users.  I'd rather educate them, empower them if you will, in order for
them to use CVS in a more intelligent/correct manner.  Once they know
where to find CVS information, and learn about its more powerfull features,
they will become much more usefull CVS users.  (Why the *hell* do they
need "su" access anyhow, do these programs need "root" privilidge to
test/run?!?  If so, I now know why the security industry is a growing
field...)


> I really want to stop accessing each others' directories, that's why I
> don't want to mess with "forced distribution" of .cvsrc

There is no need to do this.  As I've said many times before, communication
is the key.  I'm sure you have manuals or documents of some sort, which tell
people what proceedures are to be followed.  Include the use of CVS among
them.  Put up a developers FAQ/web-page, telling people the most salient
points they should know...

--Toby.

Reply via email to