Thank you so much, Eric. Your solution makes perfect sense to me. Being a system
administrator and not a full-time programmer, I forgot about the usefulness of make.
Thanks, again.
-Kevin
>>> Eric Siegerman <[EMAIL PROTECTED]> 02/05/03 05:18PM >>>
On Wed, Feb 05, 2003 at 04:54:15PM -0500, KEVIN ZEMBOWER wrote:
> How would I use CVS to organized a project called "prds" which had
> source code in /usr/local/src/prds and documentation in
> /usr/share/docs/prds and library files in /var/lib/prds? If I can
> understand this, I can probably translate it to my problem.
You'd organize it as:
<project-root>/
src/
doc/
lib/
Then write a top-level Makefile (or similar) containing an
"install" target to copy everything to where it needs to be in
production. In other words, pretty much the way the CVS
distribution itself is organized.
N.B.: <project-root> isn't any particular directory. By default
it will have the same name as the CVS module (probably "prds" in
your case), but each developer is free to override that by giving
their working directory any name they like, and to put it
anywhere they like.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED]
| | /
A distributed system is one on which I cannot get any work done,
because a machine I have never heard of has crashed.
- Leslie Lamport
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
