Hello,

I am new at this stuff, but I think I have thoroughly checked manuals,
FAQs, and this list's archive.  I have found discussions that come close
but none that address this issue.

I have modules defined such that I can check out the following structure:

test/
    CVS/
    a.c
    myproj/
           CVS/
           hello.c
           README.txt

This works fine, but there are other files on the same level as a.c, and
another directory on that level also (parallel to myproj/).  The problem
comes when I want to update.  In the test directory described above, I type
cvs update.  The problem is that when I do this I get the other files and
directories on that level (i.e. I end up with the following structure)

test/
    CVS/
    a.c
    b.c
    myproj/
           CVS/
           hello.c
           README.txt
           a-subdir/
                   CVS/
                    whatever.c
                    subdirsubdir/
                              CVS/
                              random.c
           b-subdir/
                    CVS/
                    fish.c
           c-subdir/
                    CVS/
                    color.c
     TestCVS/
            CVS/
            binaryfile.zip

When I try to use the module name with update (i.e. cvs update test) from
within the directory, I get
cvs update: nothing known about test

If I try cvs update test from the level above test, I get
cvs update: cannot open CVS/Entries for reading: No such file or directory
cvs update: nothing known about testtop
cvs [update aborted]: cannot open CVS/Root: No such file or directory

Is it just the case that once I check things out to this level using this
module, I need to update one file/submodule at a time, or am I mis-using
the modules feature and/or options in CVS???

My modules are defined as:
toplev -a a.c
testtop -a toplev myproj/hello.c myproj/README.txt

Any help (or pointers if this is already discussed somewhere I couldn't
find) would be greatly appreciated.  Thanks!!!

Keith Richeson
Phone: 919-543-2676
Fax: 919-543-7421
[EMAIL PROTECTED]

"A problem well stated is a problem half solved"


_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to