The CVS FAQ says:
By default, the `modules' file behaves as described above. If the
modules file is very large, storing it as a flat text file may make
looking up modules slow (I'm not sure whether this is as much of a
concern now as when CVS first evolved this feature; I haven't seen
benchmarks). Therefore, by making appropriate edits to the CVS source
code one can store the modules file in a database which implements the
ndbm interface, such as Berkeley db or GDBM. If this option is in use,
then the modules database will be stored in the files `modules.db',
`modules.pag', and/or `modules.dir'.
Is there any further info on configuring CVS to use gdbm? Especially,
benchmarks?
luke
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs