[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multi-user working directories

From: Wayne_Johnson
Subject: Re: Multi-user working directories
Date: Tue, 9 Jan 2001 11:02:18 -0600

Agreed.  A shared account is plan B.

Here's the scenario:

A customer reports a problem.  It is assigned to a developer.  This developer
has their own private sandbox in which to develop a fix.  When they've come up
with a fix, tested and reviewed it, and then checked it in.  The developer then
needs to build, what in the mainframe world is called a PTF, a set of executable
(and other) files that include the fix.  This PTF is suppose to be just the
minimal changed code.  Mainframe programmers are very paranoid, if it wasn't
fixed, don't touch it.  Used to be that some wouldn't even allow modules to be
replaced, you had to patch the code in place.  Yuk.

This developer now goes to the common build sandbox, does an update to pick up
this (and maybe other) fixes, and then a make.  After the build completes, they
pack up the changed executables (AKA binaries) and other files, and create a PTF
package for distribution to customers.

The problem here is that there are multiple developers and CVS will not even do
a diff for a developer if it's been checked out by another.
Thank you all for your time and patience.  Looks like there might be an opening
here for a future feature.  Something like an override userid option or
environment variable.  Something that says, use this userid, not the one on
CVS/Root.  If I ever get the MVS port completed (it's working but barely), I
might look into this.  I can foresee other places where this would be handy.
For instance, John calls up and says he broke foobar.c and asks you if you could
look at it and see what's wrong.  You cd over to his directory and look at his
code and can't see anything either.  You try and do a cvs diff to see what he's

Thanks again.

"Derek R. Price" <address@hidden> on 01/09/2001 10:19:28 AM

To:   Wayne Johnson/MINN/address@hidden
cc:   Alex Holst <address@hidden>, address@hidden
Subject:  Re: Multi-user working directories

address@hidden wrote:

> The problem here is that we can't check it out every time we want to
> the code.  There are thousands of modules that would need to be re-compiled.
> need to update the code that was already checked out and run make to build the
> updated modules.  We then will distribute the changed executables.  The
> is there could be any of several people who need to do this.

If you don't want each person who may have to do it to check out a single "build
space" once which they then reuse each time they need to rebuild, I'd probably
with a shared account or group access to your shared build space.  I usually
to avoid the shared account, myself, for security reasons.


Derek Price                      CVS Solutions Architect ( )
mailto:address@hidden     OpenAvenue ( )
I will not barf unless I'm sick.
I will not barf unless I'm sick.
I will not barf unless I'm sick...

          - Bart Simpson on chalkboard, _The Simpsons_

Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]