NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/gnu/misc/discuss/4431

Internet Message Format | 1993-01-12 | 1.6 KB

Path: sparky!uunet!noc.near.net!hri.com!spool.mu.edu!mixcom.com!calyx.corp
From: [e-mail] (calyx.corp)
Newsgroups: gnu.misc.discuss
Subject: CVS: need help w/ export, network access, shared modules
Message-ID: <[e-mail]>
Date: 12 Jan 93 22:44:04 GMT
Sender: [e-mail] (Calyx Corp.)
Distribution: usa
Organization: Milwaukee Internet Xchange BBS, Milwaukee, WI U.S.A.
Lines: 24

Our company is switching over from using SCCS to CVS.
Does anyone use CVS?  I have some questions about it's use, and would
apprieciate any suggestions.

[1] How do you deal with "shared" modules, like shared header files?
If we set up a module for an entire software package, with submodules
underneath it, including a module for the header files shared across the
entire package, do you always checkout/update the shared headers module
when you checkout/update a submodule of the package?  The simplest solution
seems to be to always checkout/update the entire package, but our development
department (8 programmers) works on a single Unix machine, and we don't have
enough hard disk space to let everyone checkout their own private copies of
our main software package (which is currently non-modular and huge).

[2] How do you deal with network access?  The simplest solution appears to
be to put the source repository on NFS, but are there any other ways?
We can barely keep our current heterogeous network functional, and it doesn't
look like we'll have the time or money to put NFS on all our machines
(we're just now getting rid of machines that don't even support
rlogin or rcp....)

- Nels Olsen
--
[e-mail]