Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I am curious about if/how CVSACL handles modules (i.e. those defined in
CVSROOT/modules). Can anyone shed some light on this? I hope to find out
about both regular modules and alias modules (with the -a switch).
My initial tests with alias modules seem to suggest that the "-f
aliasmodname" qualifier to "cvs racl" will cause the ACL to be applied
to the files aliased by the module; and the "-d aliasmodname" will cause
it to be applied to the directories aliased by the module. But I don't
know whether to trust this behavior or to fear it!
Am I trying to hammer a square peg in a round hole here by trying to use
CVSACL for these purposes? Or is there a proper way to make this work?
Thanks in advance!