Re: problems when editing modules file

[Larry Jones]

Jay Glanville writes:
> 
> However, If I do another checkout of the CVSROOT module and look at the
> modules file, I can see my changes.  It's just that my changes to the
> modules,v file aren't getting to the modules file. What gives?

When you commit files in CVSROOT, you should see a message from CVS that
it's "Rebuilding administrative file database" -- I'm guessing you
didn't see that because it didn't happen.  Usually that's caused by
checking out something similar enough to CVSROOT to get the right files,
but sufficiently different to prevent CVS from noticing that it really
is CVSROOT.  In the future, make sure you check out exactly CVSROOT:
make sure it's all in uppercase, make sure you're using forward slashes
and not backslashes, and make sure you aren't using any extra slashes.

For now, you can get CVS to rebuild the administrative files by doing
"cvs init" on the repository.  (In an existing repository, all init does
is add any missing administrative files and then rebuilds the database.)

-Larry Jones

Nobody knows how to pamper like a Mom. -- Calvin