info-cvs
[Top][All Lists]
Advanced

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

Weird module behavior


From: Robert Kerr
Subject: Weird module behavior
Date: Fri, 14 Sep 2001 15:09:58 -0600 (MDT)

Hi all,
I have a strange problem with cvs, and I'm hoping I can get some guidance
from the list.

I have a repository on a machine (call it dumbo).  I have a major project
in it--call it gipper.
Gipper has some subdirectories in it (suba and subb).
I've set up the modules file so that we can do a cvs checkout on gipper,
and get all the files in the main gipper directory along with the suba and
subb directories.  Now there's been a request to make a module that just
checks out suba and subb by themselves, plus the makefile from the main
directory.  Okay, so I've set up a module (call it freddy), that checks
out the makefile, suba and subb and puts them in a directory called
freddy.  So far, so good.
Now comes the fun stuff.
On dumbo, if I do an update in the freddy directory, cvs looks at the
makefile, and the two subdirectories and that's it.  But if I'm doing this
remotely, when I do an update in freddy, it looks at the subdirectories
and the makefile, and then proceeds to add in the other files from the
main directory, which I don't want.

I thought it was a problem with versions (dumbo is running 1.11, whereas
my remote computer is running 1.10.8).  So I downloaded and compiled
1.11.p1 for my remote computer, but it still exhibits the same behavior.
Now, on a different remote computer it actually does the update correctly.
Does anyone have any ideas what is happening?

-- 
-bob


Every day it's the same thing -- variety.  I want something different.
**********************************************************************
* Robert Kerr, The morphing guy.  *    MS 0847 Sandia National Labs  *
* address@hidden               *    Albuquerque NM 87185-0847     *
* address@hidden             *      Phone: (505) 844-8606       *
* http://www.et.byu.edu/~kerrr    *      Fax: (505) 844-9297         *
**********************************************************************






reply via email to

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