Re: Overriding CVS/Root with pserver

[Todd Denniston]

"Greg A. Woods" wrote:
> 
> [ On Thursday, May 1, 2003 at 10:48:09 (-0600), Ed wrote: ]
> > Subject: Re: Overriding CVS/Root with pserver
> >
> > On Thursday May 1 2003 10:37, Greg A. Woods wrote:
> > > [ On Thursday, May 1, 2003 at 10:10:16 (-0600), Ed wrote: ]
> > >
> > > > Subject: Overriding CVS/Root with pserver
> > > >
> > > > Suppose I have a working directory on host devbox, and the CVS/Root
> > > > admin file contains ":pserver:address@hidden:/cvsroot".  Is there a way
> > > > for address@hidden to override this to login and/or commit changes to
> > > > this working directory as, say, address@hidden, *without* modifying
> > > > the .../CVS/Root setting?  It seems any CVSROOT env setting is ignored
> > > > during login.  I know this is not considered kosher, but is there a
> > > > way?
> > > However why can't you just copy the working directory and modify the
> > > CVS/Root files in the copy?
> >
> > The number of files and directories and distinct cvsserver users needing to
> > do this makes that impractical.
> 
> Then I would humbly suggesst that using CVS is impractical for your purposes.
> 
> Every user really should have their own private working directory, and
> there really shouldn't be any problem with any user having multiple
> working directories if they need them.
> 
> I keep several active working directories with source trees for whole
> operating systems in them (that's at least tens of thousands of files
> each).
> 

With diskspace being as cheap as it is today, and NIS(+) allowing user setup
propagation, I am led to think you are doing DB or website design work. And a
quick google on bluepolka.net seems to also point in this direction.

could it be that you are attempting to keep code and DBs in the same
directories?

If so, have you looked at the possibility of separating them so each user can
work on their copy of the code and access a common checked out DB, which one
person does the checkin's on the DB? i.e. you might be looking for a way to do
a solution, to a problem which has a different & better/easier, long term,
solution.

does each user need the WHOLE directory tree to do their work, cvs can allow
you to checkout only the portion of the directory tree you need, if the tree is
properly setup.

Note, DB can be replaced with pics/pdf/other binaries above.

Or as greg points out abstractly, you might be using the wrong tool for the
job. As there are varied people here who have worked on many jobs, if you
explain why you have the problem with cvs (again number of files*users does not
cut it) someone here may be able to point you down the paths they have already
proven to work.