Re: cvs update doesn't use modules?

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark E. Hamilton <address@hidden> writes:

> I don't know why I've never noticed this before, but I've just
> discovered that 'cvs update' won't update modules. We have a module
> that specifically excludes certain sub-directories, and a user wanted
> to use 'cvs update -d -P module' to ensure that he got any new
> directories in the sub-directories the module did check out. This
> didn't work, and of course updating the directory checks out the
> excluded stuff.

The CVSROOT/modules file is really just a way to specify aliases to
files and directories you want collected. If you look at the CVS
directory contents, it does not have any indication of the original
'module' that may have been used to checkout the directories.

> Why doesn't update use modules? 

Because CVS has no idea which module or modules may have been used for
the initial checkout.

> Is this something that will be fixed in 1.12?

It is not currently fixed and I know of no plans to do anything in this
area.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFFgksPCg7APGsDnFERAmeaAKCIQhQe+i1XRFbvo9m2cCxf37DrAgCgvk7H
BD0po+4zSW/n5sEywX8QMNc=
=64Vp
-----END PGP SIGNATURE-----